X-Original-To: pgsql-performance@postgresql.org Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by postgresql.org (Postfix) with ESMTP id B65684763BD for ; Thu, 6 Mar 2003 16:13:33 -0500 (EST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id h26LDCP03630; Thu, 6 Mar 2003 16:13:12 -0500 (EST) From: Bruce Momjian Message-Id: <200303062113.h26LDCP03630@candle.pha.pa.us> Subject: Re: OIDs as keys In-Reply-To: <19293.1046877640@sss.pgh.pa.us> To: Tom Lane Date: Thu, 6 Mar 2003 16:13:12 -0500 (EST) Cc: Neil Conway , Christopher Kings-Lynne , daniel alvarez , Richard Huxton , PostgreSQL Performance X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200303/47 X-Sequence-Number: 1345 Tom Lane wrote: > Neil Conway writes: > > 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? > > Seems better than cluttering the CREATE TABLE itself with them, I guess. 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. -- 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