From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Enabling Checksums |
Date: | 2013-03-07 04:12:27 |
Message-ID: | CAM-w4HPmofBAmQD83CkO8C+6DP5c3WvGrewzaJOHB7V98KXsNg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Mar 6, 2013 at 11:04 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> When we first talked about this feature for
>> 9.2, we were going to exclude hint bits from checksums, in order to
>> avoid this issue; what happened to that?
>
> I don't think anyone ever thought that was a particularly practical
> design. I certainly don't.
Really? I thought it was pretty much the consensus for a good while.
The main problem it ran into was that we kept turning up hint bits
that we didn't realize we had. Index line pointers turned out to have
hint bits, page headers have one, and so on. As long as it was just
the heap page per-tuple transaction hint bits it seemed plausible to
just skip them or move them all to a contiguous blocks. Once it
started to look like the checksumming code had to know about every
data structure on every page it seemed a bit daunting. But that wasn't
something we realized for quite a long time.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2013-03-07 04:17:12 | Re: Enabling Checksums |
Previous Message | Greg Smith | 2013-03-07 03:30:50 | Re: Enabling Checksums |