| From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Neil Conway <neilc(at)samurai(dot)com>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: introduce "default_use_oids" |
| Date: | 2003-12-01 22:35:17 |
| Message-ID: | 20031201223517.GM16484@dcc.uchile.cl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kurt Roeckx | 2003-12-01 22:42:19 | Re: 7.4 shared memory error on 64-bit SPARC/Solaris 5.8 |
| Previous Message | Bruce Momjian | 2003-12-01 22:34:30 | Re: improve psql lo_* help |