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 | 20140116164039.GF21170@alap3.anarazel.de обсуждение исходный текст |
Ответ на | 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 11:35:00 -0500, Stephen Frost wrote: > * Andres Freund (andres@2ndquadrant.com) wrote: > > So, if we want to support antything but a) relative to pgdata b) > > relative to postgresql.conf it needs to be configurable at startup > > time. Possibly with an added initdb switch to set the location. > > How would an initdb switch be better than an option in postgresql.conf? > That sounds very backwards to me. If you meant a *postmaster*/pg_ctl > option, that would make some sense to me, for folks who would like to > avoid having a single postgresql.conf at all... Don't know if that > would work today or not tho. Oh, I was thinking of initdb option being complementary to a postgresql.conf option, just setting the path in the generated postgresql.conf. That way distributions wouldn't have to muck around in the generated config anymore. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: