From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Curt Sampson <cjs(at)cynic(dot)net> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Detecting corrupted pages earlier |
Date: | 2003-02-18 04:04:46 |
Message-ID: | 20608.1045541086@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Curt Sampson <cjs(at)cynic(dot)net> writes:
> On Mon, 17 Feb 2003, Tom Lane wrote:
>> Postgres has a bad habit of becoming very confused if the page header of
>> a page on disk has become corrupted.
> What typically causes this corruption?
Well, I'd like to know that too. I have seen some cases that were
identified as hardware problems (disk wrote data to wrong sector, RAM
dropped some bits, etc). I'm not convinced that that's the whole story,
but I have nothing to chew on that could lead to identifying a software
bug.
> If it's any kind of a serious problem, maybe it would be worth keeping
> a CRC of the header at the end of the page somewhere.
See past discussions about keeping CRCs of page contents. Ultimately
I think it's a significant expenditure of CPU for very marginal returns
--- the layers underneath us are supposed to keep their own CRCs or
other cross-checks, and a very substantial chunk of the problem seems
to be bad RAM, against which occasional software CRC checks aren't
especially useful.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Anuradha Ratnaweera | 2003-02-18 04:26:46 | Group by, count, order by and limit |
Previous Message | Bruce Momjian | 2003-02-18 03:33:58 | Re: lock method |