Re: can't find files in pg_clog and invalid page headers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Adam Kavan <akavan(at)cox(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: can't find files in pg_clog and invalid page headers
Date: 2003-08-18 17:37:46
Message-ID: 28350.1061228266@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Adam Kavan <akavan(at)cox(dot)net> writes:
> At 03:19 PM 8/14/03 -0400, Tom Lane wrote:
>> I think you've got a hardware problem. Have you run memtest86 or
>> badblocks lately?

> My machine has passed badblocks and memtest86 with flying colors. To fix
> the table I did a TRUNCATE on it which seems to have worked, but I'm left
> with a couple of questions. First, will a TRUNCATEd page wind up in
> another table and break it or is that bit fixed for good.

TRUNCATE would just return the page back to the filesystem, which would
eventually reallocate it to some other file (or even the same file).

If it was a one-time problem then it's gone, but I still suspect that
your hardware dropped some bits, and if so it may do so again.

FWIW, I have heard reports of disk problems that were not found by
badblocks unless you used the "destructive test" option.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jenny Zhang 2003-08-18 17:55:57 factors determining the execution plan
Previous Message Tom Lane 2003-08-18 17:23:40 Re: Cache lookup failed?