Skip site navigation (1) Skip section navigation (2)

Re: Block-level CRC checks

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 (view raw or flat)
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).



In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2008-10-01 13:54:36
Subject: Re: Common Table Expressions (WITH RECURSIVE) patch
Previous:From: pgsqlDate: 2008-10-01 13:29:01
Subject: Re: Block-level CRC checks

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group