Re: Re: Doc patch making firm recommendation for setting the value of commit_delay

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Noah Misch <noah@leadboat.com>, Peter Geoghegan <peter.geoghegan86@gmail.com>, PG Hackers <pgsql-hackers@postgresql.org>
Date: 2013-03-18T19:07:24Z
Lists: pgsql-hackers
On Fri, Mar 15, 2013 at 05:47:30PM -0400, Tom Lane wrote:
> Noah Misch <noah@leadboat.com> writes:
> > I'm marking this patch Ready for Committer, qualified with a recommendation to
> > adopt only the wal.sgml changes.
> 
> I've committed this along with some further wordsmithing.  I kept
> Peter's change to pg_test_fsync's default -s value; I've always felt
> that 2 seconds was laughably small.  It might be all right for very
> quick-and-dirty tests, but as a default value, it seems like a poor
> choice, because it's at the very bottom of the credible range of
> choices.

Agreed, 2 seconds was at the bottom.  The old behavior was very slow so
I went low.  Now that we are using it, 5 secs makes sense.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +


Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Add microsecs/op display to pg_test_fsync utility