On 11/24/2014 07:29 AM, Stephen Frost wrote: >> > > > 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.
The main reason why disabling auto.conf was found not to be worthwhile is that anyone with superuser rights can *already* change the config by using ALTER DATABASE and ALTER ROLE, and that's a LOT less auditable than pg.auto.conf is. Heck, we don't even have a good system view for SET parameters on DB objects. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
