pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron Mayer <ron@intervideo.com>
To: pgsql-performance@postgresql.org
Cc: daniel alvarez <d-alvarez@gmx.de>
Cc: Richard Huxton <dev@archonet.com>
Subject: Re: OIDs as keys
Date: Thu, 27 Feb 2003 17:51:13 -0800
Message-ID: <POEDIPIPKGJJLDNIEMBEIEJGCEAA.ron@intervideo.com> (raw)
In-Reply-To: <9113.1046329568@sss.pgh.pa.us>

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.




view thread (26+ messages)  latest in thread

Message-ID: <POEDIPIPKGJJLDNIEMBEIEJGCEAA.ron@intervideo.com>
Permalink:  ../POEDIPIPKGJJLDNIEMBEIEJGCEAA.ron@intervideo.com/
Also on:    postgresql.org/message-id/POEDIPIPKGJJLDNIEMBEIEJGCEAA.ron@intervideo.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: ron@intervideo.com, d-alvarez@gmx.de, dev@archonet.com
  Subject: Re: OIDs as keys
  In-Reply-To: <POEDIPIPKGJJLDNIEMBEIEJGCEAA.ron@intervideo.com>
  References: <9113.1046329568@sss.pgh.pa.us> <POEDIPIPKGJJLDNIEMBEIEJGCEAA.ron@intervideo.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox