I see we still are dumping CREATE TABLE using WITH OIDS, rather than
using the more portable SET default_with_oids.  This needs fixing.


Alvaro Herrera wrote:
> On Mon, Dec 01, 2003 at 05:07:40PM -0500, Bruce Momjian wrote:
> > Neil Conway wrote:
> > > This patch adds a new GUC var, "default_use_oids", which follows the
> > > proposal for eventually deprecating OIDs on user tables that I posted
> > > earlier to pgsql-hackers. pg_dump now always specifies WITH OIDS or
> > > WITHOUT OIDS when dumping a table. The documentation has been updated.
> > > 
> > > Comments are welcome.
> Hum, sorry to be late, but wasn't one of the supposed strenghts of
> pg_dump supposed to be that you could take a dump and load it on a
> different RDBMS?  I haven't tried it so I don't know if it works, but
> this patch takes out the ability to do that -- no one else will accept
> WITH/WITHOUT OIDS, so the dump will have to be modified.  Is a switch
> provided to stop the emission of those modifiers?
> -- 
> Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
> "Escucha y olvidar?s; ve y recordar?s; haz y entender?s" (Confucio)

  Bruce Momjian                        |  http://candle.pha.pa.us
  [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 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Reply via email to