From: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Turning recovery.conf into GUCs |
Date: | 2014-11-24 16:50:06 |
Message-ID: | 1416847806066-5828052.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2014-11-24 16:59:04 | Re: test_shm_mq failing on anole (was: Sending out a request for more buildfarm animals?) |
Previous Message | Stephen Frost | 2014-11-24 16:50:00 | Re: superuser() shortcuts |