X-Original-To: pgsql-performance@postgresql.org Received: from bob.samurai.com (bob.samurai.com [205.207.28.75]) by postgresql.org (Postfix) with ESMTP id 168D1476447 for ; Thu, 6 Mar 2003 16:23:08 -0500 (EST) Received: from DU150.N224.ResNet.QueensU.CA (DU150.N224.ResNet.QueensU.CA [130.15.224.150]) by bob.samurai.com (Postfix) with ESMTP id 944CF1F2A; Thu, 6 Mar 2003 16:23:03 -0500 (EST) Subject: Re: OIDs as keys From: Neil Conway To: Bruce Momjian Cc: Tom Lane , Christopher Kings-Lynne , daniel alvarez , Richard Huxton , PostgreSQL Performance In-Reply-To: <200303062113.h26LDCP03630@candle.pha.pa.us> References: <200303062113.h26LDCP03630@candle.pha.pa.us> Content-Type: text/plain Organization: Message-Id: <1046985774.10528.57.camel@tokyo> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 06 Mar 2003 16:22:54 -0500 Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/50 X-Sequence-Number: 1348 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... Cheers, Neil -- Neil Conway || PGP Key ID: DB3C29FC