Re: Should commit_delay be PGC_SIGHUP?

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: Should commit_delay be PGC_SIGHUP?
Дата
Msg-id CAM3SWZTVf+AKMD55YOq9CfHnMzTdObweQ1Q7euxmrDw3XXvAHA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Should commit_delay be PGC_SIGHUP?  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On Thu, Mar 21, 2013 at 6:27 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> This may be true, but so what?  We don't generally restrict changing
> GUC settings on the grounds that people probably won't wish to do so
> because it isn't useful.  We restrict it in situations where it is not
> technically possible or is liable to be harmful.

Sure, but that isn't what I'm concerned about. I'm concerned about
people being lulled into a false sense of security about setting
commit_delay to 0 locally. If they do that, their actual additional
delay at commit time may well be only marginally less than the full
commit_delay, and will only rarely actually be 0.

-- 
Peter Geoghegan



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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]
Следующее
От: Dimitri Fontaine
Дата:
Сообщение: Re: [COMMITTERS] pgsql: Fix "element <@ range" cost estimation.