From: | C GG <cgg0007(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PANIC: could not open critical system index 2662 |
Date: | 2018-08-06 21:51:40 |
Message-ID: | CAJXW-z-BbxYa-M7K1NSwi2rLTBAsObWhqmcHpS3DbP+37LUvuw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Aug 4, 2018 at 11:13 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> C GG <cgg0007(at)gmail(dot)com> 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.
>
>
I appreciate the reality check, Tom. I turned it every which way, but no
matter what, before I can issue a statement it will crash. Looks pretty
bleak.
If that doesn't work, it's time to hire professional help --- there are
> several companies that specialize in PG data recovery.
>
>
@Community: Does anyone know of a data recovery company that will work on a
per-incident basis?
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ravi Krishna | 2018-08-06 22:21:51 | Re: PANIC: could not open critical system index 2662 |
Previous Message | Devrim Gündüz | 2018-08-06 21:38:38 | Re: Who and How is responsible for released installations packages and 3rd party packs? (e.g. on https://yum.postgresql.org/9.6/redhat/rhel-7.3-x86_64/) |