pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: 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, 6 Mar 2003 16:11:05 -0500 (EST)
Message-ID: <200303062111.h26LB5J03462@candle.pha.pa.us> (raw)
In-Reply-To: <9227.1046331043@sss.pgh.pa.us>

Tom Lane wrote:
> "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.

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



view thread (26+ messages)  latest in thread

Message-ID: <200303062111.h26LB5J03462@candle.pha.pa.us>
Permalink:  ../200303062111.h26LB5J03462@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200303062111.h26LB5J03462@candle.pha.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: pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, chriskl@familyhealth.com.au, d-alvarez@gmx.de, dev@archonet.com
  Subject: Re: OIDs as keys
  In-Reply-To: <200303062111.h26LB5J03462@candle.pha.pa.us>
  References: <9227.1046331043@sss.pgh.pa.us> <200303062111.h26LB5J03462@candle.pha.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