X-Original-To: pgsql-performance@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 734FF474E4F for ; Thu, 27 Feb 2003 02:06:26 -0500 (EST) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with SMTP id 23729-08 for ; Thu, 27 Feb 2003 02:06:15 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id A075A474E42 for ; Thu, 27 Feb 2003 02:06:15 -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 h1R7685u009114; Thu, 27 Feb 2003 02:06:08 -0500 (EST) To: "Christopher Kings-Lynne" Cc: "daniel alvarez" , "Richard Huxton" , pgsql-performance@postgresql.org Subject: Re: OIDs as keys 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> Comments: In-reply-to "Christopher Kings-Lynne" message dated "Thu, 27 Feb 2003 15:00:04 +0800" Date: Thu, 27 Feb 2003 02:06:08 -0500 Message-ID: <9113.1046329568@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new X-Archive-Number: 200302/221 X-Sequence-Number: 1277 "Christopher Kings-Lynne" 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