pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Neil Conway <neilc@samurai.com>
Cc: 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: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: OIDs as keys
Date: Thu, 6 Mar 2003 20:50:36 -0500 (EST)
Message-ID: <200303070150.h271oaW02436@candle.pha.pa.us> (raw)
In-Reply-To: <1046985774.10528.57.camel@tokyo>

Neil Conway wrote:
> On Thu, 2003-03-06 at 16:13, Bruce Momjian wrote:
> > It would be good to somehow SET the use_oids GUC value on restore start,
> > and just use SET when the table is different than the default, but then
> > there is no mechanism to do that when you restore a single table.
> 
> What if the default value changes?
> 
> IMHO, running a SET per CREATE TABLE isn't too ugly...

Not ugly, but a little noisy.  However, my idea of having a single SET
at the top is never going to work, so I don't have a better idea.

The killer for me is that you are never going to know the GUC default
when you are loading, so we are _always_ going to have that SET for each
table.

I suppose we could set the default to off, and set it ON in the dump
only when we want OID.  If they set GUC to on, they will get oid's from
the load, but it will cut down on the cruft and over time, they will
only have the SET for cases where they really want an oid.

-- 
  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: <200303070150.h271oaW02436@candle.pha.pa.us>
Permalink:  ../200303070150.h271oaW02436@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200303070150.h271oaW02436@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, neilc@samurai.com, tgl@sss.pgh.pa.us, chriskl@familyhealth.com.au, d-alvarez@gmx.de, dev@archonet.com
  Subject: Re: OIDs as keys
  In-Reply-To: <200303070150.h271oaW02436@candle.pha.pa.us>
  References: <1046985774.10528.57.camel@tokyo> <200303070150.h271oaW02436@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