| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Stefan Kaltenbrunner" <stefan(at)kaltenbrunner(dot)cc>, "Feng Chen" <fchen(at)covergence(dot)com>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Marc Schablewski" <ms(at)clickware(dot)de>, "Decibel!" <decibel(at)decibel(dot)org>, <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: [SPAM] Re: BUG #3484: Missing pg_clog file / corrupt index |
| Date: | 2007-08-24 16:46:35 |
| Message-ID: | 87k5rkzxqs.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Remember that the xmin/xmax fields are basically the first thing we can
> check with any degree of strictness when examining a tuple. This means that
> if a page is partially clobbered, but not in a way that sets off the
> invalid-page-header checks, then the odds are very high that the first
> detectable sign of trouble will be references to transaction numbers that
> are far away from what the system is really using.
I'm increasingly thinking that one of the first things I'll suggest putting
into 8.4 is a per-page checksum after all. It was talked about a while back
and people thought it was pointless but I think the number of reports of
hardware and kernel bugs resulting in zeroed and corrupted pages has been
steadily going up. If not in total than as a percentage of the total problems.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Feng Chen | 2007-08-24 17:41:31 | Re: [SPAM] Re: [SPAM] Re: BUG #3484: Missing pg_clog file / corrupt index |
| Previous Message | Tom Lane | 2007-08-24 16:10:55 | Re: [SPAM] Re: BUG #3484: Missing pg_clog file / corrupt index |