| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au> |
| 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 03:59:19 |
| Message-ID: | 12024.961991959@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Bitmead | 2000-06-26 04:02:40 | Re: About the pid and opts files |
| Previous Message | Chris Bitmead | 2000-06-26 03:47:23 | Re: About the pid and opts files |