Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1flyFS-0004FA-C5 for pgsql-general@arkaria.postgresql.org; Sat, 04 Aug 2018 15:13:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1flyFQ-0001CU-75 for pgsql-general@arkaria.postgresql.org; Sat, 04 Aug 2018 15:13:40 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1flyFP-0001CN-Rd for pgsql-general@lists.postgresql.org; Sat, 04 Aug 2018 15:13:40 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1flyFJ-00087o-Ht for pgsql-general@postgresql.org; Sat, 04 Aug 2018 15:13:38 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w74FDVs1022585; Sat, 4 Aug 2018 11:13:31 -0400 From: Tom Lane To: C GG cc: pgsql-general@postgresql.org Subject: Re: PANIC: could not open critical system index 2662 In-reply-to: References: Comments: In-reply-to C GG message dated "Sat, 04 Aug 2018 10:45:59 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <22583.1533395611.1@sss.pgh.pa.us> Date: Sat, 04 Aug 2018 11:13:31 -0400 Message-ID: <22584.1533395611@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk C GG writes: > When trying to restart the PostgreSQL 9.2 database for our JIRA > installation, we're getting > "PANIC: could not open critical system index 2662" ... I've tried various > things like turning on zero_damaged_pages but postmaster still crashes on > connect when attempting to pg_dump. 2662 is pg_class_oid_index :-( Try starting a single-user backend with the ignore-system-indexes flag, and doing "REINDEX INDEX pg_class_oid_index". If that works, I'd try reindexing the rest of the system just to see how bad things are. If that doesn't work, it's time to hire professional help --- there are several companies that specialize in PG data recovery. regards, tom lane