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 B26B4529F2 for ; Wed, 3 Aug 2005 11:32:26 -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 71225-10 for ; Wed, 3 Aug 2005 14:32:17 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 7807F52800 for ; Wed, 3 Aug 2005 11:32:15 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j73EWDmQ001151; Wed, 3 Aug 2005 10:32:13 -0400 (EDT) To: Brock Williams Cc: pgsql-admin@postgresql.org Subject: Re: FATAL: cache lookup failed for access method 6881280 In-reply-to: <42F043D8.5030707@cotcomsol.com> References: <42F008F2.60509@cotcomsol.com> <26599.1123037702@sss.pgh.pa.us> <42F043D8.5030707@cotcomsol.com> Comments: In-reply-to Brock Williams message dated "Tue, 02 Aug 2005 22:11:04 -0600" Date: Wed, 03 Aug 2005 10:32:13 -0400 Message-ID: <1150.1123079533@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.567 tagged_above=0 required=5 tests=AWL, SUBJ_HAS_UNIQ_ID X-Spam-Level: X-Archive-Number: 200508/31 X-Sequence-Number: 18350 Brock Williams writes: > 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 Hmm, this is quite odd. You have Item 22 -- Length: 156 Offset: 4760 (0x1298) Flags: USED XMIN: 1 CMIN: 0 XMAX: 0 CMAX|XVAC: 0 Block Id: 1 linp Index: 22 Attributes: 24 Size: 32 infomask: 0x0910 (HASOID|XMIN_COMMITTED|XMAX_INVALID) 1298: 01000000 00000000 00000000 00000000 ................ 12a8: 00000100 16001800 10092000 4f410000 .......... .OA.. 12b8: 70675f70 726f635f 70726f6e 616d655f pg_proc_proname_ 12c8: 61726773 5f6e7370 5f696e64 65780000 args_nsp_index.. 12d8: 00000000 00000000 00000000 00000000 ................ 12e8: 00000000 00000000 00000000 00000000 ................ 12f8: 0b000000 00000000 01000000 00006900 ..............i. -------- 1308: 01000000 00000000 94000000 00c0da44 ...............D -------- 1318: 01000000 00000000 00006900 04000000 ..........i..... -------- 1328: 00000000 00000000 00000000 ............ A non-broken 8.0 installation has Item 22 -- Length: 156 Offset: 4760 (0x1298) Flags: USED XMIN: 1 CMIN: 0 XMAX: 0 CMAX|XVAC: 0 Block Id: 1 linp Index: 22 Attributes: 24 Size: 32 infomask: 0x0910 (HASOID|XMIN_COMMITTED|XMAX_INVALID) 1298: 01000000 00000000 00000000 00000000 ................ 12a8: 00000100 16001800 10092000 4f410000 .......... .OA.. 12b8: 70675f70 726f635f 70726f6e 616d655f pg_proc_proname_ 12c8: 61726773 5f6e7370 5f696e64 65780000 args_nsp_index.. 12d8: 00000000 00000000 00000000 00000000 ................ 12e8: 00000000 00000000 00000000 00000000 ................ 12f8: 0b000000 00000000 01000000 93010000 ................ -------- 1308: 4f410000 00000000 94000000 0060da44 OA...........`.D -------- 1318: 00000000 00000000 00006900 04000000 ..........i..... -------- 1328: 00000000 00000000 00000000 ............ where I underlined the parts that are different. The first different word is the relam field, which leads directly to the reported error message, and the other two changes are bad news as well. (Note: the difference at offset 1314 is the reltuples field, which could legitimately be different across installations, and your value matches the other pg_proc indexes so it's presumably OK.) I have no idea what happened here ... but if you can put those values back the way they were you'll probably be all right. You'll need to shut down the postmaster before editing the file (else it may have the page cached in shared memory), and if there is a pg_internal.init file in the same directory delete it. regards, tom lane