>> 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
Your optimism is showing ;-). XLogInsert routinely shows up as a major
CPU hog in any update-intensive test, and AFAICT that's mostly from the
CRC calculation for WAL records.
We could possibly use something cheaper than a real CRC, though. A
word-wide XOR (ie, effectively a parity calculation) would be sufficient
to detect most problems.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Paul Schlie||Date: 2008-10-01 14:49:24|
|Subject: Re: Block-level CRC checks|
|Previous:||From: Tom Lane||Date: 2008-10-01 14:11:09|
|Subject: Re: Common Table Expressions (WITH RECURSIVE) patch |