| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Neil Conway <neilc(at)samurai(dot)com>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: introduce "default_use_oids" |
| Date: | 2003-12-02 12:26:39 |
| Message-ID: | 200312021226.hB2CQdN13481@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
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 | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-12-02 12:39:56 | Re: YA Cygwin DLLIMPORT patch |
| Previous Message | Peter Eisentraut | 2003-12-02 09:30:46 | Re: introduce "default_use_oids" |