From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: postgresql.auto.conf and reload |
Date: | 2014-07-08 17:13:58 |
Message-ID: | 53BC26D6.4090403@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 07/06/2014 01:27 AM, Christoph Berg wrote:
> Another could be that during initdb all the uncommented settings be
>> written to postgresql.auto.conf file rather than to postgresql.conf.
>> I think we can do this by changing code in initdb.c->setup_config().
>> This will ensure that unless user is changing settings in a mixed way
>> (some by Alter System and some manually by editing postgresql.conf),
>> there will no such problem.
There is no reasonable way for us to prevent issues for users who are
manually changing both pg.conf and pg.auto.conf. Users should stick to
one or the other method of management (or, thirdly, using conf.d); if
they mix methods, we can't prevent confusion at restart time and we
shouldn't try.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2014-07-08 17:41:25 | Re: Securing "make check" (CVE-2014-0067) |
Previous Message | Jeff Janes | 2014-07-08 17:11:26 | Re: Supporting Windows SChannel as OpenSSL replacement |