Re: Spread checkpoint sync

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>
To: Greg Smith <greg@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org
Date: 2011-02-01T18:30:53Z
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. Add new buffers_backend_fsync field to pg_stat_bgwriter.

Greg Smith wrote:
> Greg Smith wrote:
> > I think the right way to compute "relations to sync" is to finish the 
> > sorted writes patch I sent over a not quite right yet update to already
> 
> Attached update now makes much more sense than the misguided patch I 
> submitted two weesk ago.  This takes the original sorted write code, 
> first adjusting it so it only allocates the memory its tag structure is 
> stored in once (in a kind of lazy way I can improve on right now).  It 
> then computes a bunch of derived statistics from a single walk of the 
> sorted data on each pass through.  Here's an example of what comes out:

In that patch, I would like to see a meta-comment explaining why the
sorting is happening and what we hope to gain.

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

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