Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it
От | Andres Freund |
---|---|
Тема | Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it |
Дата | |
Msg-id | 20140116135505.GA4498@alap3.lan обсуждение исходный текст |
Ответ на | Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it (Stephen Frost <sfrost@snowman.net>) |
Ответы |
Re: Why conf.d should be default, and auto.conf and
recovery.conf should be in it
|
Список | pgsql-hackers |
On 2014-01-16 08:34:23 -0500, Stephen Frost wrote: > Peter, > > * Peter Eisentraut (peter_e@gmx.net) wrote: > > Then one might as well argue that the pg_db_role_setting table be > > relocated to /etc. It's the same facility, only on a slightly different > > level. The fact that postgresql.auto.conf looks the same as a > > plain-text configuration file is an implementation detail. We could > > have chosen some binary format instead. > > I argued quite a bit that we should be looking at moving more things > into the catalog tables and pulling them out of postgresql.conf, > reducing that down to just what's required to be there, rather than this > nasty hack where SQL commands are modifying text config files. Given that the majority didn't seem to be convinced by this and that the feature was written differently this isn't a convincing argument for the location of the file given the current feature, no? Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: