Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
От | Andres Freund |
---|---|
Тема | Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |
Дата | |
Msg-id | 20130801231608.GA7262@alap2.anarazel.de обсуждение исходный текст |
Ответ на | Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) (Stephen Frost <sfrost@snowman.net>) |
Ответы |
Re: Re: ALTER SYSTEM SET command to change postgresql.conf
parameters (RE: Proposal for Allow postgresql.conf values to be changed via
SQL [review])
|
Список | pgsql-hackers |
On 2013-08-01 14:37:45 -0400, Stephen Frost wrote: > * Alvaro Herrera (alvherre@2ndquadrant.com) wrote: > > Andres Freund wrote: > > > > > Postgresql.auto.conf.d is what I'd propose, but the decision about > > > that seems to be one of the smaller problems around this feature... > > > That naming seems to make it sensible to extend other files (hba, > > > ident) similarly at a later point. > > > > I don't like this particular naming proposal, but I'm glad this patch > > finally seems to be getting somewhere. > > Yeah, also not a fan. We don't have any 'conf.d' directories in PGDATA > and I don't think we should start now. I liked Josh's suggestions of > something like "system_conf". For multiple independent config files, we > could use directories under that (eg: 'pgconf', 'pghba', 'pgident'..). People know what to expect from .d directories, that's why I suggested it, don't feel really strongly about it. I dislike naming the subdirectories pgconf/... et al though, we should reference the original files name, instead of introducing new abbreviations. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: