"Jonah H. Harris" <jonah(dot)harris(at)gmail(dot)com> writes:
> On Wed, Oct 1, 2008 at 10:27 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 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.
> I probably wouldn't compare checksumming *every* WAL record to a
> single block-level checksum.
No, not at all. Block-level checksums would be an order of magnitude
more expensive: they're on bigger chunks of data and they'd be done more
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: pgsql||Date: 2008-10-01 15:37:35|
|Subject: Re: Block-level CRC checks|
|Previous:||From: Tom Lane||Date: 2008-10-01 15:34:54|
|Subject: Re: Block-level CRC checks |