Re: CRCs (was Re: [GENERAL] Re: Loading optimization)

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: CRCs (was Re: [GENERAL] Re: Loading optimization)
Date: 2001-01-12 05:39:23
Message-ID: 200101120539.AAA29985@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

> "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> writes:
> >> Actually, I'd expect the CRC check to catch an all-zeroes page (if
> >> it fails to complain, then you misimplemented the CRC), so that would
> >> be the place to deal with it now.
>
> > I've used standard CRC32 implementation you pointed me to -:)
> > But CRC is used in WAL records only.
>
> Oh. I thought we'd agreed that a CRC on each stored disk block would
> be a good idea as well. I take it you didn't do that.

No, I thought we agreed disk block CRC was way overkill. If the CRC on
the WAL log checks for errors that are not checked anywhere else, then
fine, but I thought disk CRC would just duplicate the I/O subsystem/disk
checks.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2001-01-12 06:16:20 Re: CRCs (was Re: [GENERAL] Re: Loading optimization)
Previous Message Thomas T. Thai 2001-01-12 05:32:09 mnogosearch -- pgsql seem so slow, please help me find out why

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-01-12 05:42:39 Re: Bruce Momjian's interview in LWN.
Previous Message Bruce Momjian 2001-01-12 05:37:22 Re: alter table drop column