| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Neil Conway <neilc(at)samurai(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, 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-03 01:46:41 |
| Message-ID: | 3FCD4081.7090507@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
> 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.
OK.
> 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.
Ok, more thought is required then.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2003-12-03 02:31:20 | Re: introduce "default_use_oids" |
| Previous Message | Tom Lane | 2003-12-02 23:27:43 | Re: 7.4 shared memory error on 64-bit SPARC/Solaris 5.8 |