Re: 16-bit page checksums for 9.2 - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: 16-bit page checksums for 9.2
Date
Msg-id CA+U5nM+L_RFkiSoW7C5rYEaaQkgTnw+P3Y4yhS-S_9n1=+rsKQ@mail.gmail.com
Whole thread Raw
In response to Re: 16-bit page checksums for 9.2  (Stephen Frost <sfrost@snowman.net>)
Responses Re: 16-bit page checksums for 9.2  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Wed, Jan 4, 2012 at 1:31 PM, Stephen Frost <sfrost@snowman.net> wrote:
> Simon, all,
>
> * Simon Riggs (simon@2ndQuadrant.com) wrote:
>> (1) report all errors on a page, including errors that don't change
>> PostgreSQL data. This involves checksumming long strings of zeroes,
>> which the checksum algorithm can't tell apart from long strings of
>> ones.
>
> Do we actually know when/where it's supposed to be all zeros, and hence
> could we check for that explicitly?  If we know what it's supposed to
> be, in order to be consistent with other information, I could certainly
> see value in actually checking that.

Yes, we can. Excellent suggestion, will implement.

That means we can keep the CRC calc fast as well as check the whole of
the page inbound.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: BGWriter latch, power saving
Next
From: Amit Kapila
Date:
Subject: Regarding Checkpoint Redo Record