| From: | daniel alvarez <d-alvarez(at)gmx(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgman(at)candle(dot)pha(dot)pa(dot)us, neilc(at)samurai(dot)com, chriskl(at)familyhealth(dot)com(dot)au, dev(at)archonet(dot)com, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: OIDs as keys |
| Date: | 2003-03-08 20:16:32 |
| Message-ID: | 19376.1047154592@www68.gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> daniel alvarez <d-alvarez(at)gmx(dot)de> 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!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-03-10 16:05:21 | Re: OIDs as keys |
| Previous Message | Tom Lane | 2003-03-08 20:09:15 | Re: OIDs as keys |