> If I want to develop a portable application or I want to port an
> application, then I am of course only going to use portable constructs,
> that is, tables and views, and possibly sequences. I'm not talking theory
> here -- I've actually done it and made several changes to pg_dump along
> the way to make the output portable. This is an actual feature that is
> being destroyed.
OK.
> I'm sure there are other ways to phase out OIDs in dumps. For example, we
> could set the default mode at the top (easily deleted, much safer than
> running a global search and replace) and then add WITH/WITHOUT OIDS only
> to those tables that deviate from the default.
Ok, more thought is required then.
Chris