X-Original-To: pgsql-performance@postgresql.org Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by postgresql.org (Postfix) with SMTP id 9EBD3474E42 for ; Sat, 8 Mar 2003 15:16:32 -0500 (EST) Received: (qmail 22581 invoked by uid 0); 8 Mar 2003 20:16:32 -0000 Date: Sat, 8 Mar 2003 21:16:32 +0100 (MET) From: daniel alvarez To: Tom Lane Cc: pgman@candle.pha.pa.us, neilc@samurai.com, chriskl@familyhealth.com.au, dev@archonet.com, pgsql-performance@postgresql.org MIME-Version: 1.0 References: <10510.1047154155@sss.pgh.pa.us> Subject: Re: OIDs as keys X-Priority: 3 (Normal) X-Authenticated-Sender: #0002681999@gmx.net X-Authenticated-IP: [217.185.184.254] Message-ID: <19376.1047154592@www68.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200303/69 X-Sequence-Number: 1367 > 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. Ouch. Why is this? Doesn't it read the config because of portability reasons? -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!