X-Original-To: pgsql-performance@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 8D22A474E42 for ; Thu, 27 Feb 2003 22:10:45 -0500 (EST) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with SMTP id 53332-02 for ; Thu, 27 Feb 2003 22:10:28 -0500 (EST) Received: from torque.intervideoinc.com (mail.intervideo.com [206.112.112.151]) by postgresql.org (Postfix) with ESMTP id D6652475E52 for ; Thu, 27 Feb 2003 20:59:25 -0500 (EST) Received: from ronpc [63.68.5.2] by torque.intervideoinc.com (SMTPD32-5.05) id A6FCC7013C; Thu, 27 Feb 2003 18:18:36 -0800 From: "Ron Mayer" To: Cc: "daniel alvarez" , "Richard Huxton" Subject: Re: OIDs as keys Date: Thu, 27 Feb 2003 17:51:13 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <9113.1046329568@sss.pgh.pa.us> X-Virus-Scanned: by amavisd-new X-Archive-Number: 200302/238 X-Sequence-Number: 1294 Tom wrote: > >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. Has there been any talk about adding a flag to pg_dump to explicitly ask for a standard format? (sql3? sql99? etc?) Ideally for me, such a flag would produce a "portable" dump file of the subset that did follow the standard, and also produce a separate log file that could contain any constructs that could not be standardly dumped. If such a flag existed, it might be the easiest way to load to other databases, and people might be less opposed to plastering more postgres specific stuff to the default format. If I were going to try to write portable dumps for other databases, I'd want as few postgresisms in the big file as possible. The separate log file would make it easier for me to make hand-ported separate files to set up functions, views, etc. Yes, I know that would restrict the functionality I could depend on, including types, sequences, etc. However if I were in an environment where developers did prototyping on postgres / mssql /etc and migrated functionality to whatever the company's official standard system was, I think developers would want to constrain themselves to standards as much as possible, and this option may help them do so. Ron PS: I'm not sure if I'm volunteering or not, unless someone tells me how easy/hard it would be. Last thing I tried was harder than it first appeared.