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

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Noah Misch <noah@leadboat.com>
Cc: Peter Geoghegan <peter.geoghegan86@gmail.com>, PG Hackers <pgsql-hackers@postgresql.org>
Date: 2013-03-15T21:47:30Z
Lists: pgsql-hackers
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.

			regards, tom lane


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