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 D469A52B38 for ; Tue, 2 Aug 2005 20:59:54 -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 48431-02 for ; Tue, 2 Aug 2005 23:59:50 +0000 (GMT) Received: from brookie.cotcomsol.com (LanIP100.CottonwoodComputer-gw.bil.oneeighty.com [216.187.178.100]) by svr1.postgresql.org (Postfix) with ESMTP id 704DB529AE for ; Tue, 2 Aug 2005 20:59:47 -0300 (ADT) Received: from [172.16.4.10] (timon.cotcomsol.com [216.187.178.98]) (authenticated bits=0) by brookie.cotcomsol.com (8.12.10/8.12.3) with ESMTP id j72NxkEk071776 for ; Tue, 2 Aug 2005 17:59:46 -0600 (MDT) (envelope-from brock@cotcomsol.com) Message-ID: <42F008F2.60509@cotcomsol.com> Date: Tue, 02 Aug 2005 17:59:46 -0600 From: Brock Williams Organization: Cottonwood Computer Solutions, Inc. User-Agent: Mozilla Thunderbird 1.0 (X11/20050318) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: FATAL: cache lookup failed for access method 6881280 X-Enigmail-Version: 0.90.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamd / ClamAV version 0.74, clamav-milter version 0.74a on brookie.cotcomsol.com X-Virus-Status: Clean X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.172 tagged_above=0 required=5 tests=FORGED_RCVD_HELO, SUBJ_HAS_UNIQ_ID X-Spam-Level: * X-Archive-Number: 200508/21 X-Sequence-Number: 18340 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 I get the message any way I try to access it: remotely via TCP, locally on the db server, as well as with a single-user mode postgres command. Any ideas what could be the cause, or what I could do to fix it? All the other (30+) databases in the cluster appear to be perfectly fine. Thanks, Brock - -- Brock Williams brock@cotcomsol.com Cottonwood Computer Solutions, Inc. www.cotcomsol.com 406-896-4910 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFC8AjygMCVEEcrWuIRAr0rAJ0TJwvWDxxNSYq2nib2P2ix2IT9ggCeNixx UvLi8JF08ga2PiBW6hr0DaU= =Wum4 -----END PGP SIGNATURE-----