Horton
Menu

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

Stephen Frost <sfrost@snowman.net>

View thread
From: Stephen Frost <sfrost@snowman.net>
To: Peter Geoghegan <peter@2ndquadrant.com>
Cc: Magnus Hagander <magnus@hagander.net>, Greg Smith <greg@2ndquadrant.com>, Albe Laurenz <laurenz.albe@wien.gv.at>, PG Hackers <pgsql-hackers@postgresql.org>
Date: 2012-11-16T01:20:51Z
Lists: pgsql-hackers 
* Peter Geoghegan (peter@2ndquadrant.com) wrote:
> I am inclined to agree. I did attempt to use the instrumentation
> macros to have commit_delay set adaptively at runtime, which would
> have at least addressed this concern, but that just didn't work as
> well as this.

Setting it at run-time was actually my first thought on this.  I'm
disappointed to hear that it didn't work out well.

	Thanks,

		Stephen

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