RE: Re: TODO list - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject RE: Re: TODO list
Date
Msg-id 8F4C99C66D04D4118F580090272A7A234D3381@sectorbase1.sectorbase.com
Whole thread Raw
In response to TODO list  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Re: TODO list  (ncm@zembu.com (Nathan Myers))
Re: Re: TODO list  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> If the reason that a block CRC isn't on the TODO list is that Vadim
> objects, maybe we should hear some reasons why he objects?  Maybe 
> the objections could be dealt with, and everyone satisfied.

Unordered disk writes are covered by backing up modified blocks
in log. It allows not only catch such writes, as would CRC do,
but *avoid* them.

So, for what CRC could be used? To catch disk damages?
Disk has its own CRC for this.

Vadim


pgsql-hackers by date:

Previous
From: ncm@zembu.com (Nathan Myers)
Date:
Subject: Re: Re: TODO list
Next
From: ncm@zembu.com (Nathan Myers)
Date:
Subject: Re: Re: TODO list