pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Brock Williams <brock@cotcomsol.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: FATAL: cache lookup failed for access method 6881280
Date: Wed, 03 Aug 2005 11:05:16 -0600
Message-ID: <42F0F94C.5090503@cotcomsol.com> (raw)
In-Reply-To: <1150.1123079533@sss.pgh.pa.us>
References: <42F008F2.60509@cotcomsol.com>
	<26599.1123037702@sss.pgh.pa.us>
	<42F043D8.5030707@cotcomsol.com>
	<1150.1123079533@sss.pgh.pa.us>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tom:

Thanks for the help.  I hex-edited the file back to what you
recommended, and it did in fact work.  I did a dump/restore on the
database just to be safe as well.

Brock

Tom Lane wrote:
> Brock Williams <brock@cotcomsol.com> 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

- --
Brock Williams  brock@cotcomsol.com
Cottonwood Computer Solutions, Inc.
www.cotcomsol.com 406-896-4910
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)

iD8DBQFC8PlMgMCVEEcrWuIRArLtAJ0fSPeN7z6a1XfiIuXqMEBizAS4wACgnLcp
hb+XBsKHmi7ToPf4p+D0Btg=
=hjNE
-----END PGP SIGNATURE-----



view thread (7+ messages)

Message-ID: <42F0F94C.5090503@cotcomsol.com>
Permalink:  ../42F0F94C.5090503@cotcomsol.com/
Also on:    postgresql.org/message-id/42F0F94C.5090503@cotcomsol.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: brock@cotcomsol.com
  Subject: Re: FATAL: cache lookup failed for access method 6881280
  In-Reply-To: <42F0F94C.5090503@cotcomsol.com>
  References: <42F008F2.60509@cotcomsol.com> <26599.1123037702@sss.pgh.pa.us> <42F043D8.5030707@cotcomsol.com> <1150.1123079533@sss.pgh.pa.us> <42F0F94C.5090503@cotcomsol.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox