| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | CRCs (was Re: [GENERAL] Re: Loading optimization) |
| Date: | 2001-01-12 02:55:58 |
| Message-ID: | 14019.979268158@sss.pgh.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.
Do we want to consider doing this (and forcing another initdb)?
Or shall we say "too late for 7.1"?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joseph Shraibman | 2001-01-12 04:01:31 | Re: Java Classes |
| Previous Message | Bruce Momjian | 2001-01-12 02:22:14 | Interview in Japan |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lamar Owen | 2001-01-12 02:59:58 | Re: AW: Re: GiST for 7.1 !! |
| Previous Message | Lincoln Yeoh | 2001-01-12 02:37:39 | Re: Lock on arbitrary string feature |