X-Original-To: pgsql-performance@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 4A0ED475CBC for ; Thu, 27 Feb 2003 02:42:28 -0500 (EST) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with SMTP id 31627-10 for ; Thu, 27 Feb 2003 02:42:17 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 6DCD3475E1E for ; Thu, 27 Feb 2003 02:30:50 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h1R7Uh5u009228; Thu, 27 Feb 2003 02:30:43 -0500 (EST) To: "Christopher Kings-Lynne" Cc: "daniel alvarez" , "Richard Huxton" , pgsql-performance@postgresql.org Subject: Re: OIDs as keys In-reply-to: <044801c2de30$93d71ca0$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> <9113.1046329568@sss.pgh.pa.us> <044801c2de30$93d71ca0$6500a8c0@fhp.internal> Comments: In-reply-to "Christopher Kings-Lynne" message dated "Thu, 27 Feb 2003 15:19:33 +0800" Date: Thu, 27 Feb 2003 02:30:43 -0500 Message-ID: <9227.1046331043@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new X-Archive-Number: 200302/222 X-Sequence-Number: 1278 "Christopher Kings-Lynne" writes: >> 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. > Ummm...what about SERIAL columns, ALTER TABLE / SET STATS, SET STORAGE, > custom types, 'btree' in CREATE INDEX, SET SEARCH_PATH, '::" cast operator, > stored procedures, rules, etc. - how is adding WITH OIDS going to change > that?! 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. I'm not necessarily wedded to the above argument myself, mind you; but it is a valid point that needs to be weighed in the balance of what we're trying to accomplish. The bottom line is that "code first, design later" is no way to approach this problem. regards, tom lane