RE: Re: TODO list

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: Re: TODO list
Date: 2001-04-05 21:27:48
Message-ID: 8F4C99C66D04D4118F580090272A7A234D3381@sectorbase1.sectorbase.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Myers 2001-04-05 21:38:34 Re: Re: TODO list
Previous Message Nathan Myers 2001-04-05 21:01:10 Re: Re: TODO list