On Mon, Nov 30, 2009 at 3:27 PM, Heikki Linnakangas
> Simon Riggs wrote:
>> * We reserve enough space on a disk block for a CRC check. When a dirty
>> block is written to disk we calculate and annotate the CRC value, though
>> this is *not* WAL logged.
> Imagine this:
> 1. A hint bit is set. It is not WAL-logged, but the page is dirtied.
> 2. The buffer is flushed out of the buffer cache to the OS. A new CRC is
> calculated and stored on the page.
> 3. Half of the page is flushed to disk (aka torn page problem). The CRC
> made it to disk but the flipped hint bit didn't.
> You now have a page with incorrect CRC on disk.
This is probably a stupid question, but why doesn't the other half of
the page make it to disk? Somebody pulls the plug first?
In response to
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 2009-12-01 12:07:25|
|Subject: Re: CommitFest status/management|
|Previous:||From: Bruce Momjian||Date: 2009-12-01 12:05:47|
|Subject: Re: Block-level CRC checks|