Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 61F40632530 for ; Wed, 30 Jun 2010 17:30:24 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 39529-02 for ; Wed, 30 Jun 2010 20:30:16 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 45E3F633034 for ; Wed, 30 Jun 2010 17:30:17 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o5UKUF4c016650; Wed, 30 Jun 2010 16:30:15 -0400 (EDT) To: Nathan Robertson cc: Kevin Grittner , pgsql-admin@postgresql.org Subject: Re: cache lookup failed for index In-reply-to: References: <4C2B02040200002500032D63@gw.wicourts.gov> <4C2B0AEF0200002500032D75@gw.wicourts.gov> <4C2B21A00200002500032D8D@gw.wicourts.gov> <11712.1277914463@sss.pgh.pa.us> <12643.1277917499@sss.pgh.pa.us> <15355.1277925611@sss.pgh.pa.us> Comments: In-reply-to Nathan Robertson message dated "Wed, 30 Jun 2010 16:05:26 -0400" Date: Wed, 30 Jun 2010 16:30:15 -0400 Message-ID: <16649.1277929815@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201006/234 X-Sequence-Number: 35012 Nathan Robertson writes: > OK, as postgres user: > -bash-3.2$ postgres -O -P -D /tmp/database webapp > FATAL: cache lookup failed for index 2662 Even with -P? Wow, that's bad. This DB may be just toast I'm afraid. But try it like this: postgres -O -P -D /tmp/database -c log_error_verbosity=verbose webapp This should give you the exact location of the error, which will give us a bit better clue what's failing. regards, tom lane