From: | pgsql(at)mohawksoft(dot)com |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Hannu Krosing" <hannu(at)2ndquadrant(dot)com>, pgsql(at)mohawksoft(dot)com, "Decibel!" <decibel(at)decibel(dot)org>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Block-level CRC checks |
Date: | 2008-10-01 13:38:54 |
Message-ID: | 39053.71.232.149.185.1222868334.squirrel@mail.mohawksoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Hannu Krosing <hannu(at)2ndQuadrant(dot)com> writes:
>> So I don't think that this is a space issue.
>
> No, it's all about time penalties and loss of concurrency.
I don't think that the amount of time it would take to calculate and test
the sum is even important. It may be in older CPUs, but these days CPUs
are so fast in RAM and a block is very small. On x86 systems, depending on
page alignment, we are talking about two or three pages that will be "in
memory" (They were used to read the block from disk or previously
accessed).
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-10-01 13:54:36 | Re: Common Table Expressions (WITH RECURSIVE) patch |
Previous Message | pgsql | 2008-10-01 13:29:01 | Re: Block-level CRC checks |