From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |
Date: | 2013-07-26 00:52:37 |
Message-ID: | 51F1C855.2010207@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 07/25/2013 02:02 PM, Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Thu, Jul 18, 2013 at 6:03 PM, Alvaro Herrera
>> <alvherre(at)2ndquadrant(dot)com> wrote:
>>> Josh Berkus escribi�:
>>>> We are missing one feature, which is the ability to relocate the
>>>> postgresql.auto.conf file if relocating it is desireable according to
>>>> some sysadmin spec.
>
>> My thought is that people might put postgresql.conf in a directory
>> that only contains configuration files and isn't writeable by the
>> postgres user. So I would expect to find postgresql.auto.conf in the
>> data directory always.
>
> Yeah, exactly. I think putting it anywhere but $PGDATA is a bad idea,
> and a sysadmin who thinks he knows better probably doesn't.
Please see Greg Smith's fairly strong arguments for putting it in the
config/ directory.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tomonari Katsumata | 2013-07-26 02:19:50 | Re: comment for "fast promote" |
Previous Message | Fabrízio de Royes Mello | 2013-07-26 00:44:09 | Re: Patch to add support of "IF NOT EXISTS" to others "CREATE" statements |