Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]
Дата
Msg-id CA+TgmoYb_1vdJWTS_nx2FnpSdk6KOE+wjfVTt_JQQN4HkUb8Dw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]  (Andres Freund <andres@2ndquadrant.com>)
Ответы Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]  (Kevin Grittner <kgrittn@ymail.com>)
Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]  (Andres Freund <andres@2ndquadrant.com>)
Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]  (Boszormenyi Zoltan <zb@cybertec.at>)
Список pgsql-hackers
On Thu, Jan 24, 2013 at 12:39 PM, Andres Freund <andres@2ndquadrant.com> wrote:
> More people seem to have voted for the single file approach but I still
> haven't understood why...

Me neither.  Having an include directory seems good, but I can't think
why we'd want to clutter it up with a bajillion automatically
generated files.  One .auto file that gets overwritten at need seems
way nicer.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Francois Tigeot
Дата:
Сообщение: Re: SYSV shared memory vs mmap performance
Следующее
От: Noah Misch
Дата:
Сообщение: Re: Visual Studio 2012 RC