Horton

Re: Latch for the WAL writer - further reducing idle wake-ups.

Peter Geoghegan <peter@2ndquadrant.com>

View thread
From: Peter Geoghegan <peter@2ndquadrant.com>
To: PG Hackers <pgsql-hackers@postgresql.org>
Cc: Magnus Hagander <magnus@hagander.net>, Robert Haas <robertmhaas@gmail.com>
Date: 2012-05-08T23:48:40Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Make bgwriter sleep longer when it has no work to do, to save electricity.

On 9 May 2012 00:21, Peter Geoghegan <peter@2ndquadrant.com> wrote:
> Yes, there is some checking of flags before the potential ResetLatch()
> call, which may be acted on. The code there is almost identical to
> that of the extant bgwriter code. I was under the impression that this
> did not amount to a race, though it's rather late now, and I'm feeling
> under the weather, so I have not taken steps to verify that I have it
> right. Arguably, you'd want somebody's SetLatch call to be ignored if

Sent too early. That should be: Arguably, you'd want somebody's
SetLatch call to be ignored under the circumstances that that could
happen in both the bgwriter, and the WALWriter within my recent patch.

-- 
Peter Geoghegan       http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services