Re: Improving postgresql.conf
От | Greg Stark |
---|---|
Тема | Re: Improving postgresql.conf |
Дата | |
Msg-id | 87fz8v7344.fsf@stark.xeocode.com обсуждение исходный текст |
Ответ на | Re: Improving postgresql.conf (Andreas Pflug <pgadmin@pse-consulting.de>) |
Список | pgsql-hackers |
Andreas Pflug <pgadmin@pse-consulting.de> writes: > Tom Lane wrote: > > >Andreas Pflug <pgadmin@pse-consulting.de> writes: > > > >> How about *requiring* to set any variable, at least to xxx='default'? > > > >Don't like that ... we are not in the fascism business here ;-). It would just make it too hard to add new variables. Nobody would be able to upgrade without adding those variables to their config files. That might make sense for major new features that require hands-on involvement, but postgres tries to avoid that in favour of having everything just work without intervention. And you don't want every user to have to explicitly enable every new feature when upgrading. Besides, often new variables are just new debugging hooks like enable_hash_join or such that users shouldn't even have to know about until they need it. -- greg
В списке pgsql-hackers по дате отправления: