Re: WALWriteLock contention - Mailing list pgsql-hackers

From Robert Haas
Subject Re: WALWriteLock contention
Date
Msg-id CA+TgmoZi1DkkYAMpbtwi0OSWFpxx6tU8YOtJYfcMfuvg-31QEA@mail.gmail.com
Whole thread Raw
In response to Re: WALWriteLock contention  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, May 15, 2015 at 1:09 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> WALWriteLock contention is measurable on some workloads.  In studying
>> the problem briefly, a couple of questions emerged:
>
>> 1. Doesn't it suck to rewrite an entire 8kB block every time, instead
>> of only the new bytes (and maybe a few bytes following that to spoil
>> any old data that might be there)?
>
> It does, but it's not clear how to avoid torn-write conditions without
> that.

Can you elaborate?   I don't understand how repeatedly overwriting the
same bytes with themselves accomplishes anything at all.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: ERROR: cannot GetMultiXactIdMembers() during recovery
Next
From: Robert Haas
Date:
Subject: Re: PATCH: adaptive ndistinct estimator v4