X-Original-To: pgsql-performance@postgresql.org Received: from bob.samurai.com (bob.samurai.com [205.207.28.75]) by postgresql.org (Postfix) with ESMTP id 32014475EFB for ; Wed, 5 Mar 2003 08:54:58 -0500 (EST) Received: from DU150.N224.ResNet.QueensU.CA (DU150.N224.ResNet.QueensU.CA [130.15.224.150]) by bob.samurai.com (Postfix) with ESMTP id BA86A1E10; Wed, 5 Mar 2003 08:55:01 -0500 (EST) Subject: Re: OIDs as keys From: Neil Conway To: Tom Lane Cc: Christopher Kings-Lynne , daniel alvarez , Richard Huxton , PostgreSQL Performance In-Reply-To: <9227.1046331043@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> <044801c2de30$93d71ca0$6500a8c0@fhp.internal> <9227.1046331043@sss.pgh.pa.us> Content-Type: text/plain Organization: Message-Id: <1046872498.10615.17.camel@tokyo> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 05 Mar 2003 08:54:58 -0500 Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/25 X-Sequence-Number: 1323 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. 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. Cheers, Neil -- Neil Conway || PGP Key ID: DB3C29FC