From: | Brock Williams <brock(at)cotcomsol(dot)com> |
---|---|
To: | |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: FATAL: cache lookup failed for access method 6881280 |
Date: | 2005-08-03 04:11:04 |
Message-ID: | 42F043D8.5030707@cotcomsol.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tried to post directy to the list but I got a bounce back. Must be too
big...
Here it is posted to my web site:
http://www.cotcomsol.com/~brock/postgresql_debug.txt
Thanks for the help,
Brock
Tom Lane wrote:
> 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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)
iD8DBQFC8EPYgMCVEEcrWuIRAhCcAJ9RZEMrKFpbRfjHOVW1Vfj6eys+VgCfaKhA
2EV6MSgumAvDv+Lv0k2WrdI=
=IZnE
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Steulet Grégory | 2005-08-03 08:46:34 | hot backup |
Previous Message | Tom Lane | 2005-08-03 02:55:02 | Re: FATAL: cache lookup failed for access method 6881280 |