Peter Eisentraut wrote:
> 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.
> 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.

Agreed.  By using SET, you could still pipe the file through another
database --- the SETs would fail, but the CREATE TABLE commands would
work.  With WITH/WITHOUT OIDS, the CREATE TABLEs would fail.

  Bruce Momjian                        |
  [EMAIL PROTECTED]               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
      subscribe-nomail command to [EMAIL PROTECTED] so that your
      message can get through to the mailing list cleanly

Reply via email to