Re: Should commit_delay be PGC_SIGHUP? - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Should commit_delay be PGC_SIGHUP?
Date
Msg-id CAM3SWZTVf+AKMD55YOq9CfHnMzTdObweQ1Q7euxmrDw3XXvAHA@mail.gmail.com
Whole thread Raw
In response to Re: Should commit_delay be PGC_SIGHUP?  (Robert Haas <robertmhaas@gmail.com>)
List 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 by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]
Next
From: Dimitri Fontaine
Date:
Subject: Re: [COMMITTERS] pgsql: Fix "element <@ range" cost estimation.