From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Alex Shulgin <ash(at)commandprompt(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Turning recovery.conf into GUCs |
Date: | 2014-11-24 14:53:18 |
Message-ID: | 20141124145318.GX1639@alvin.alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stephen Frost wrote:
> * Amit Kapila (amit(dot)kapila16(at)gmail(dot)com) 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?
>
> Last I paid attention to this, there was a clear way to disable the
> inclusion of postgresql.auto.conf in the postgresql.conf. If that's
> gone, then there is a serious problem. Administrators who manage their
> postgresql.conf (eg: through a CM system like puppet or chef..) must
> have a way to prevent other changes.
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 think if you want puppet or chef etc you'd add postgresql.auto.conf as
a config file in those systems, so that ALTER SYSTEM is reflected there.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2014-11-24 15:13:58 | Re: Turning recovery.conf into GUCs |
Previous Message | Christoph Berg | 2014-11-24 14:36:18 | Re: test_shm_mq failing on anole (was: Sending out a request for more buildfarm animals?) |