X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 72DF4529AD for ; Wed, 3 Aug 2005 02:12:08 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 23732-08 for ; Wed, 3 Aug 2005 05:12:05 +0000 (GMT) Received: from syslog1.bresnan.net (syslog1.bresnan.net [69.145.232.10]) by svr1.postgresql.org (Postfix) with ESMTP id 61B0A529C7 for ; Wed, 3 Aug 2005 02:12:04 -0300 (ADT) Received: from [69.145.248.18] (HELO cluster1.bresnan.net) by syslog1.bresnan.net (CommuniGate Pro SMTP 4.3.6) with ESMTP id 1886334 for pgsql-admin@postgresql.org; Tue, 02 Aug 2005 23:12:04 -0600 Received: from [69.145.71.97] (HELO [192.168.0.115]) by fe-3.cluster1.bresnan.net (CommuniGate Pro SMTP 4.2.10) with ESMTP id 54615375 for pgsql-admin@postgresql.org; Tue, 02 Aug 2005 23:12:05 -0600 Message-ID: <42F043D8.5030707@cotcomsol.com> Date: Tue, 02 Aug 2005 22:11:04 -0600 From: Brock Williams User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050730) X-Accept-Language: en-us, en MIME-Version: 1.0 Cc: pgsql-admin@postgresql.org Subject: Re: FATAL: cache lookup failed for access method 6881280 References: <42F008F2.60509@cotcomsol.com> <26599.1123037702@sss.pgh.pa.us> In-Reply-To: <26599.1123037702@sss.pgh.pa.us> X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.122 tagged_above=0 required=5 tests=SUBJ_HAS_UNIQ_ID X-Spam-Level: * X-Archive-Number: 200508/25 X-Sequence-Number: 18344 -----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 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-----