Horton

Re: WALInsertLock tuning

Jeff Janes <jeff.janes@gmail.com>

View thread
From: Jeff Janes <jeff.janes@gmail.com>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2011-06-06T21:09:35Z
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. Introduce compact WAL record for the common case of commit (non-DDL).

On Mon, Jun 6, 2011 at 11:27 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
>
> But that even assumes we write the unzeroed data at the end of the
> buffer. We don't. We only write data up to the end of the WAL record
> on the current page, unless we do a continuation record,

I see no codepath in XLogWrite which writes anything other than full
buffer pages.

Cheers,

Jeff