From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Brock Williams <brock(at)cotcomsol(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: FATAL: cache lookup failed for access method 6881280 |
Date: | 2005-08-03 02:55:02 |
Message-ID: | 26599.1123037702@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Brock Williams <brock(at)cotcomsol(dot)com> writes:
> I'm getting this message when I try to access one of the databases in
> my cluster:
> FATAL: cache lookup failed for access method 6881280
Unless you are using a custom index access method you didn't tell us
about, this is pretty strong evidence of data corruption in the pg_class
system catalog (specifically some pg_class.relam entry).
If the corruption extends only as far as those four bytes, it'd be
pretty easy to poke the correct value back in ... but it seems likely
that this is just the tip of the iceberg :-(
Please get a copy of pg_filedump from
http://sources.redhat.com/rhdb/utilities.html
and show us a dump of the pg_class file from that database (I like the
format it produces with -i -f options; note pg_class is file 1259 in all
known PG versions).
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Brock Williams | 2005-08-03 04:11:04 | Re: FATAL: cache lookup failed for access method 6881280 |
Previous Message | Chris Travers | 2005-08-03 00:37:36 | Re: FATAL: cache lookup failed for access method 6881280 |