X-Original-To: pgsql-performance@postgresql.org Received: from jester.inquent.com (unknown [216.208.117.7]) by postgresql.org (Postfix) with ESMTP id 7D08C4762C7 for ; Wed, 5 Mar 2003 09:29:38 -0500 (EST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by jester.inquent.com (8.12.6/8.12.6) with ESMTP id h25E5uve019457; Wed, 5 Mar 2003 09:05:56 -0500 (EST) (envelope-from rbt@rbt.ca) Subject: Re: OIDs as keys From: Rod Taylor To: Neil Conway Cc: Tom Lane , Christopher Kings-Lynne , daniel alvarez , Richard Huxton , Postgresql Performance In-Reply-To: <1046872498.10615.17.camel@tokyo> 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> <044801c2de30$93d71ca0$6500a8c0@fhp.internal> <9227.1046331043@sss.pgh.pa.us> <1046872498.10615.17.camel@tokyo> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-F4o8UT4G/32APyIkhcxj" Organization: Message-Id: <1046873156.18094.3.camel@jester> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 05 Mar 2003 09:05:56 -0500 X-Archive-Number: 200303/27 X-Sequence-Number: 1325 --=-F4o8UT4G/32APyIkhcxj Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2003-03-05 at 08:54, Neil Conway wrote: > On Thu, 2003-02-27 at 02:30, Tom Lane wrote: > > It's moving in the wrong direction. We've been slowly eliminating > > unnecessary nonstandardisms in pg_dump output; this puts in a new one > > in a quite fundamental place. You could perhaps expect another DB > > to drop commands it didn't understand like SET SEARCH_PATH ... but if > > it drops all your CREATE TABLEs, you ain't got much dump left to load. >=20 > Rather than specifying the use of OIDs by WITH OIDS clauses for each > CREATE TABLE in a dump, couldn't we do it by adding a SET command that > toggles the 'use_oids' GUC option prior to every CREATE TABLE? That way, > a user concerned with portability could fairly easily strip out (or just > ignore) the SET commands. Toggling the SET command prior to each table creation? Thats an excellent idea. It should also allow us to easily transition to the default being off after a release or two. --=20 Rod Taylor PGP Key: http://www.rbt.ca/rbtpub.asc --=-F4o8UT4G/32APyIkhcxj Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQA+ZgRD6DETLow6vwwRAsoHAJ0ZijQXntIDczzG5Bfo26KWVXDiPACeKgV2 z0bUAlCriwk/edBUoZYYQ70= =MSKt -----END PGP SIGNATURE----- --=-F4o8UT4G/32APyIkhcxj--