Skip site navigation (1) Skip section navigation (2)

Re: About the pid and opts files

From: Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: About the pid and opts files
Date: 2000-06-26 04:02:40
Message-ID: 3956D5E0.F7FBAE66@nimrod.itg.telecom.com.au (view raw or flat)
Thread:
Lists: pgsql-hackers
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

Responses

pgsql-hackers by date

Next:From: Ed LoehrDate: 2000-06-26 04:10:16
Subject: Re: Server process exited with status 139 (meaning?)
Previous:From: Tom LaneDate: 2000-06-26 03:59:19
Subject: Re: About the pid and opts files

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group