Re: crash-safe visibility map, take three - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: crash-safe visibility map, take three
Date
Msg-id 1291242262.21972.35.camel@jdavis-ux.asterdata.local
Whole thread Raw
In response to Re: crash-safe visibility map, take three  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: crash-safe visibility map, take three  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wed, 2010-12-01 at 15:59 -0500, Robert Haas wrote:
> As for CRCs, there's a pretty direct chain of inference here:
> 
> 1. CRCs are hard (really impossible) because we have hint bits.

I would disagree with "impossible". If we don't set hint bits during
reading; and when we do set them, we log them (including full page
writes); then we can do CRCs.

Those things have costs, but we might be willing to pay them if we had a
bulk loading strategy that avoids or mitigates the costs.

The reason we can't do CRCs now is because hint bits violate the
WAL-before-data rule; not because of hint bits themselves. We're talking
about adding another feature that breaks the rule, in a more complex way
than hint bits.

I just wanted to step back for a second and consider the problem from a
different angle before we committed to that.

Regards,Jeff Davis




pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: pg_execute_from_file review
Next
From: Greg Smith
Date:
Subject: Re: We really ought to do something about O_DIRECT and data=journalled on ext4