X-Original-To: pgsql-performance@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 72A41474E4F for ; Thu, 27 Feb 2003 02:19:05 -0500 (EST) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with SMTP id 28457-07 for ; Thu, 27 Feb 2003 02:18:54 -0500 (EST) Received: from houston.familyhealth.com.au (unknown [203.59.48.253]) by postgresql.org (Postfix) with ESMTP id 5FB64474E42 for ; Thu, 27 Feb 2003 02:18:53 -0500 (EST) Received: (from root@localhost) by houston.familyhealth.com.au (8.11.6/8.11.6) id h1R7Iq851412 for pgsql-performance@postgresql.org; Thu, 27 Feb 2003 15:18:52 +0800 (WST) (envelope-from chriskl@familyhealth.com.au) Received: from mariner (mariner.internal [192.168.0.101]) by houston.familyhealth.com.au (8.11.6/8.9.3) with SMTP id h1R7Ik751189; Thu, 27 Feb 2003 15:18:46 +0800 (WST) Message-ID: <044801c2de30$93d71ca0$6500a8c0@fhp.internal> From: "Christopher Kings-Lynne" To: "Tom Lane" Cc: "daniel alvarez" , "Richard Huxton" , 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> Subject: Re: OIDs as keys Date: Thu, 27 Feb 2003 15:19:33 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-scanner: scanned by Inflex 0.1.5c - (http://www.inflex.co.za/) X-Virus-Scanned: by amavisd-new X-Archive-Number: 200302/241 X-Sequence-Number: 1297 > 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. 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?! > 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. Sure. Chris