Re: Turning recovery.conf into GUCs - Mailing list pgsql-hackers

From David G Johnston
Subject Re: Turning recovery.conf into GUCs
Date
Msg-id 1416847806066-5828052.post@n5.nabble.com
Whole thread Raw
In response to Re: Turning recovery.conf into GUCs  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Stephen Frost wrote
> * Alvaro Herrera (

> alvherre@

> ) wrote:
>> Stephen Frost wrote:
>> > * Amit Kapila (

> amit.kapila16@

> ) wrote:
>> > > What exactly you mean by 'disable postgresql.auto.conf',  do you
>> > > mean user runs Alter System to remove that entry or manually disable
>> > > some particular entry?
>> 
>> Sigh, here we go again.  I don't think you can disable
>> postgresql.auto.conf
>> in the current code.  As I recall, the argument was that it's harder to
>> diagnose problems if postgresql.auto.conf takes effect in some system
>> but not others.
> 
> I don't buy this at all.  What's going to be terribly confusing is to
> have config changes start happening for users who are managing their
> configs through a CM (which most should be..).  ALTER SYSTEM is going to
> cause more problems than it solves.

So what happens if someone makes postgresql.auto.conf read-only (to
everyone)?

David J.




--
View this message in context: http://postgresql.nabble.com/Turning-recovery-conf-into-GUCs-tp5774757p5828052.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.



pgsql-hackers by date:

Previous
From: Alex Shulgin
Date:
Subject: Re: Replication connection URI?
Next
From: Stephen Frost
Date:
Subject: Re: superuser() shortcuts