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
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
In response to
pgsql-performance by date
|Next:||From: scott.marlowe||Date: 2003-03-10 16:55:53|
|Subject: Re: Index / Performance issues|
|Previous:||From: daniel alvarez||Date: 2003-03-08 20:16:32|
|Subject: Re: OIDs as keys|