Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) - Mailing list pgsql-hackers

From Josh Berkus
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
Msg-id 51F1C855.2010207@agliodbs.com
Whole thread Raw
In response to Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])  (Amit kapila <amit.kapila@huawei.com>)
Responses Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
List pgsql-hackers
On 07/25/2013 02:02 PM, Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Thu, Jul 18, 2013 at 6:03 PM, Alvaro Herrera
>> <alvherre@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Fabrízio de Royes Mello
Date:
Subject: Re: Patch to add support of "IF NOT EXISTS" to others "CREATE" statements
Next
From: Tomonari Katsumata
Date:
Subject: Re: comment for "fast promote"