Re: WALInsertLock tuning - Mailing list pgsql-hackers

From Tom Lane
Subject Re: WALInsertLock tuning
Date
Msg-id 8597.1307378864@sss.pgh.pa.us
Whole thread Raw
In response to WALInsertLock tuning  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: WALInsertLock tuning
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> In earlier discussions of how to improve WALInsertLock contention, it
> was observed that we must zero each new page before we advance the WAL
> insertion point.
> http://postgresql.1045698.n5.nabble.com/Reworking-WAL-locking-td1983647.html

> IMHO the page zeroing is completely unnecessary,

I don't believe it's "completely unnecessary".  It does in fact offer
additional protection against mistakenly taking stale data as valid.
You could maybe argue that the degree of safety increase isn't
sufficient to warrant the cost of zeroing the page, but you've not
offered any quantification of either the risk or the cost savings.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Range Types and extensions
Next
From: Alvaro Herrera
Date:
Subject: Re: heap vacuum & cleanup locks