pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: daniel alvarez <d-alvarez@gmx.de>
Cc: Richard Huxton <dev@archonet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: OIDs as keys
Date: Thu, 27 Feb 2003 02:30:43 -0500
Message-ID: <9227.1046331043@sss.pgh.pa.us> (raw)
In-Reply-To: <044801c2de30$93d71ca0$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>
	<9113.1046329568@sss.pgh.pa.us>
	<044801c2de30$93d71ca0$6500a8c0@fhp.internal>

"Christopher Kings-Lynne" <chriskl@familyhealth.com.au> 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.

I'm not necessarily wedded to the above argument myself, mind you;
but it is a valid point that needs to be weighed in the balance of
what we're trying to accomplish.

The bottom line is that "code first, design later" is no way to
approach this problem.

			regards, tom lane



view thread (26+ messages)  latest in thread

Message-ID: <9227.1046331043@sss.pgh.pa.us>
Permalink:  ../9227.1046331043@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/9227.1046331043@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, chriskl@familyhealth.com.au, d-alvarez@gmx.de, dev@archonet.com
  Subject: Re: OIDs as keys
  In-Reply-To: <9227.1046331043@sss.pgh.pa.us>
  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> <044801c2de30$93d71ca0$6500a8c0@fhp.internal> <9227.1046331043@sss.pgh.pa.us>

* 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