pg.ddx.io pgsql-performance@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Rod Taylor <rbt@rbt.ca>
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: 05 Mar 2003 09:05:56 -0500
Message-ID: <1046873156.18094.3.camel@jester> (raw)
In-Reply-To: <1046872498.10615.17.camel@tokyo>
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>
<1046872498.10615.17.camel@tokyo>
On Wed, 2003-03-05 at 08:54, Neil Conway wrote:
> On Thu, 2003-02-27 at 02:30, Tom Lane wrote:
> > 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.
>
> Rather than specifying the use of OIDs by WITH OIDS clauses for each
> CREATE TABLE in a dump, couldn't we do it by adding a SET command that
> toggles the 'use_oids' GUC option prior to every CREATE TABLE? That way,
> a user concerned with portability could fairly easily strip out (or just
> ignore) the SET commands.
Toggling the SET command prior to each table creation? Thats an
excellent idea. It should also allow us to easily transition to the
default being off after a release or two.
--
Rod Taylor <rbt@rbt.ca>
PGP Key: http://www.rbt.ca/rbtpub.asc
Attachments:
signature.asc (application/pgp-signature, 186B) download
view thread (26+ messages) latest in thread
Message-ID: <1046873156.18094.3.camel@jester> Permalink: ../1046873156.18094.3.camel@jester/ Also on: postgresql.org/message-id/1046873156.18094.3.camel@jester ·
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: rbt@rbt.ca, 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: <1046873156.18094.3.camel@jester> 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> <1046872498.10615.17.camel@tokyo> <1046873156.18094.3.camel@jester> * 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