| From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
|---|---|
| To: | "Greg Stark" <greg(dot)stark(at)enterprisedb(dot)com> |
| Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Block-level CRC checks |
| Date: | 2008-10-17 16:13:59 |
| Message-ID: | 36e682920810170913p3b4f0f65g433abcec52d029fa@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 17, 2008 at 12:05 PM, Greg Stark
<greg(dot)stark(at)enterprisedb(dot)com> wrote:
> Heikki had a clever idea earlier which was to have two crc checks- one which
> skips the hint bits and one dedicated to hint bits. If the second doesn't
> match we clear all the hint bits.
Sounds overcomplicated to me.
> The problem with that is that skipping the hint bits for the main crc would
> slow it down severely. It would make a lot of sense if the hint bits were
> all in a contiguous block of memory but I can't see how to make that add up.
Agreed.
--
Jonah H. Harris, Senior DBA
myYearbook.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aidan Van Dyk | 2008-10-17 16:14:08 | Re: Block-level CRC checks |
| Previous Message | Greg Stark | 2008-10-17 16:05:37 | Re: Block-level CRC checks |