On 2014-11-24 10:13:58 -0500, Stephen Frost wrote: > * Alvaro Herrera (alvhe...@2ndquadrant.com) wrote: > > Stephen Frost wrote: > > > * Amit Kapila (amit.kapil...@gmail.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 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.
I fail to see how this really has really anything to do with this topic. Obviously ALTER SYSTEM isn't a applicable solution for this as HS might not be in use or HS might not have reached consistency at that point. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
