Re: WALInsertLock tuning

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WALInsertLock tuning
Date: 2011-06-06 21:09:35
Message-ID: BANLkTinv4u3rMjjYCrJ03ihVuoC7tmn=ig@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 6, 2011 at 11:27 AM, Simon Riggs <simon(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Darren Duncan 2011-06-06 21:42:22 Re: Range Types and extensions
Previous Message David E. Wheeler 2011-06-06 20:19:48 Re: contrib/citext versus collations