Tom Lane wrote:
> Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au> writes:
> > Tom Lane wrote:
> >> Right --- it should be *possible* to change these vars, but it should
> >> take some explicit action. Having a different value in your environment
> >> at postmaster start time is probably not enough of an explicit action.
> >> This whole thread makes me more and more uncomfortable about the fact
> >> that the postmaster/backend pay attention to environment variables at
> >> all. An explicit configuration file would seem a better answer.
> > Why a configuration file? Why not a configuration table?
> Circularity. A lot of this stuff has to be known before we dare touch
> the database at all.
Aren't there other things like pg_database that survive this problem?
In response to
pgsql-hackers by date
|Next:||From: Ed Loehr||Date: 2000-06-26 04:10:16|
|Subject: Re: Server process exited with status 139 (meaning?)|
|Previous:||From: Tom Lane||Date: 2000-06-26 03:59:19|
|Subject: Re: About the pid and opts files |