Re: Block-level CRC checks - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Block-level CRC checks
Date
Msg-id 21637.1227030038@sss.pgh.pa.us
Whole thread Raw
In response to Re: Block-level CRC checks  (Aidan Van Dyk <aidan@highrise.ca>)
Responses Re: Block-level CRC checks  (Aidan Van Dyk <aidan@highrise.ca>)
List pgsql-hackers
Aidan Van Dyk <aidan@highrise.ca> writes:
> But why can't you wal-log the hint bits from the "buffered" page.  then your
> consitent.  At least as consistent as the original write was.

> So you're CRC ends up being:
>    Buffer the page
>    Calculate CRC on the buffered page
>    WAL (in bulk) the hint bits (and maybe CRC?)
>    write buffered page

The trouble here is to avoid repeated WAL-logging of the same hint bits.

(Alvaro's patch tried to do that by depending on another hint bit in the
page header, but that seems unsafe if hint bit setters aren't taking
exclusive lock.)
        regards, tom lane


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Simple postgresql.conf wizard
Next
From: "Pavel Stehule"
Date:
Subject: Re: is any reason why only one columns subselect are allowed in array()?