From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: daniel alvarez <d-alvarez@gmx.de>
Cc: Richard Huxton <dev@archonet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: OIDs as keys
Date: Thu, 27 Feb 2003 02:06:08 -0500
Message-ID: <9113.1046329568@sss.pgh.pa.us> (raw)
In-Reply-To: <040a01c2de2d$dac03780$6500a8c0@fhp.internal>
References: <200302261358.53730.dev@archonet.com>
<24135.1046271575@www36.gmx.net>
<29871.1046274964@sss.pgh.pa.us>
<032301c2de14$c64ccf70$6500a8c0@fhp.internal>
<8927.1046327718@sss.pgh.pa.us>
<040a01c2de2d$dac03780$6500a8c0@fhp.internal>
"Christopher Kings-Lynne" <chriskl@familyhealth.com.au> writes:
> The patch I submitted did not include OID stuff, I decided that it's better
> to submit orthogonal patches :)
Right. But the problem with switching the OID default is not a matter
of code --- it's of working out what the compatibility issues are.
As I recall, one thing people did not want was for pg_dump to plaster
WITH OIDS or WITHOUT OIDS on every single CREATE TABLE, as this would
pretty much destroy any shot at loading PG dumps into any other
database. What we need is an agreement on the behavior we want (making
the best possible compromise between this and other compatibility
desires). After that, the actual patch is probably trivial, while in
advance of some consensus on the behavior, offering a patch is a waste
of time.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, chriskl@familyhealth.com.au, d-alvarez@gmx.de, dev@archonet.com
Subject: Re: OIDs as keys
In-Reply-To: <9113.1046329568@sss.pgh.pa.us>
References: <200302261358.53730.dev@archonet.com> <24135.1046271575@www36.gmx.net> <29871.1046274964@sss.pgh.pa.us> <032301c2de14$c64ccf70$6500a8c0@fhp.internal> <8927.1046327718@sss.pgh.pa.us> <040a01c2de2d$dac03780$6500a8c0@fhp.internal> <9113.1046329568@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox