X-Original-To: pgsql-performance@postgresql.org Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id DD472475EE2 for ; Sat, 8 Mar 2003 15:09:35 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.8/8.12.8) with ESMTP id h28K9Fub010511; Sat, 8 Mar 2003 15:09:15 -0500 (EST) To: daniel alvarez Cc: Bruce Momjian , neilc@samurai.com, chriskl@familyhealth.com.au, dev@archonet.com, pgsql-performance@postgresql.org Subject: Re: OIDs as keys In-reply-to: <26462.1047153692@www68.gmx.net> References: <200303070150.h271oaW02436@candle.pha.pa.us> <26462.1047153692@www68.gmx.net> Comments: In-reply-to daniel alvarez message dated "Sat, 08 Mar 2003 21:01:32 +0100" Date: Sat, 08 Mar 2003 15:09:15 -0500 Message-ID: <10510.1047154155@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200303/68 X-Sequence-Number: 1366 daniel alvarez writes: >> 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. > Why isn't this done on a per-session basis? Because pg_dump can't know what the session default will be when the dump is reloaded. The scheme you are proposing will only succeed in making pg_dump unreliable. regards, tom lane