| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Neil Conway <neilc(at)samurai(dot)com>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: introduce "default_use_oids" |
| Date: | 2003-12-02 06:49:32 |
| Message-ID: | 3FCC35FC.4070107@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
> 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?
There are so many other incompatibilities in our dumps anyway!
Anyway, our first loyalty is to PostgreSQL...
If someone can't run a sed script to 's/WITH OIDS//g', then they're
going to have a LOT of problems...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-12-02 06:52:01 | Re: YA Cygwin DLLIMPORT patch |
| Previous Message | Peter Eisentraut | 2003-12-02 06:34:58 | Re: introduce "default_use_oids" |