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

From Tom Lane
Subject Re: Block-level CRC checks
Date
Msg-id 1822.1222961865@sss.pgh.pa.us
Whole thread Raw
In response to Re: Block-level CRC checks  ("Jonah H. Harris" <jonah.harris@gmail.com>)
Responses Re: Block-level CRC checks  (Aidan Van Dyk <aidan@highrise.ca>)
List pgsql-hackers
"Jonah H. Harris" <jonah.harris@gmail.com> writes:
> Just to see where to go from here... I want to make sure the options
> I've seen in this thread are laid out clearly:

> 1. Hold an exclusive lock on the buffer during the call to smgrwrite
> OR
> 2. Doublebuffer the write
> OR
> 3. Do some crufty magic to ignore hint-bit updates

Right, I think everyone agrees now that #2 seems like the most
preferable option for writing the checksum.  However, that still
leaves us lacking a solution for torn pages during a write that
follows a hint bit update.  We may end up with some "crufty
magic" anyway for dealing with that.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Treat
Date:
Subject: Re: FSM rewrite committed, loose ends
Next
From: Alvaro Herrera
Date:
Subject: Re: [GENERAL] Transactions within a function body