Just finished the video. Absolutely first rate as far as it went. I think perhaps Jim should have ended with an idealized game plan, summarizing all of this hard won knowledge as an abstract tactical roadmap. I will never have any contact will Oracle at any level, but it helps enormously for me to understand what makes Postgres distinct within the database space.
When porting a system, it's often good to get the replacement running early, in any way, shape or form. Patching over the "dual" problem is a way to there sooner. I think the point here is that patching "dual" gets you to a place where you can do more scouting. At the same time, the real portability path should prioritize drilling into the superficial Oraclysms up front, to make this kind of thing unnecessary.
