| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | daniel alvarez <d-alvarez(at)gmx(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(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-10 16:05:21 |
| Message-ID: | 200303101605.h2AG5La28728@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
daniel alvarez wrote:
> > 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?
Remember the dump output is just an SQL script, so there is no 'logic'
in the script, and it can be loaded right into psql.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | scott.marlowe | 2003-03-10 16:55:53 | Re: Index / Performance issues |
| Previous Message | daniel alvarez | 2003-03-08 20:16:32 | Re: OIDs as keys |