X-Original-To: pgsql-performance@postgresql.org Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by postgresql.org (Postfix) with ESMTP id 28B0047639F for ; Thu, 6 Mar 2003 16:11:41 -0500 (EST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id h26LB5J03462; Thu, 6 Mar 2003 16:11:05 -0500 (EST) From: Bruce Momjian Message-Id: <200303062111.h26LB5J03462@candle.pha.pa.us> Subject: Re: OIDs as keys In-Reply-To: <9227.1046331043@sss.pgh.pa.us> To: Tom Lane Date: Thu, 6 Mar 2003 16:11:05 -0500 (EST) Cc: Christopher Kings-Lynne , daniel alvarez , Richard Huxton , pgsql-performance@postgresql.org X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200303/46 X-Sequence-Number: 1344 Tom Lane wrote: > "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. Why was the schema path called search_path rather than schema_path? Standards? -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073