Re: Backport of fsync queue compaction
Andres Freund <andres@2ndquadrant.com>
From: Andres Freund <andres@2ndquadrant.com>
To: pgsql-hackers@postgresql.org
Cc: Robert Haas <robertmhaas@gmail.com>,
Greg Smith <greg@2ndquadrant.com>
Date: 2012-06-19T22:21:57Z
Lists: pgsql-hackers
On Tuesday, June 19, 2012 11:39:46 PM Robert Haas wrote: > On Tue, Jun 19, 2012 at 5:33 PM, Greg Smith <greg@2ndquadrant.com> wrote: > > In January of 2011 Robert committed > > 7f242d880b5b5d9642675517466d31373961cf98 to try and compact the fsync > > queue when clients find it full. There's no visible behavior change, > > just a substantial performance boost possible in the rare but extremely > > bad situations where the background writer stops doing fsync absorption. > > I've been running that in production at multiple locations since > > practically the day it hit this mailing list, with backports all the way > > to 8.3 being common (and straightforward to construct). I've never seen > > a hint of a problem with this new code. > > I've been in favor of back-porting this for a while, so you'll get no > argument from me. > > Anyone disagree? Not me, I have seen several sites having problems as well. +1 Andres -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Try to avoid running with a full fsync request queue.
- 7f242d880b5b 9.1.0 cited