Thread: PANIC: could not open critical system index 2662
PANIC: could not open critical system index 2662
LOG: server process (PID 44753) was terminated by signal 6: Aborted
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
LOG: all server processes terminated; reinitializing
LOG: database system was interrupted; last known up at 2018-08-04 10:04:19 EDT
LOG: database system was not properly shut down; automatic recovery in progress
LOG: record with zero length at C/8C7E28D0
LOG: redo is not required
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
C GG <cgg0007@gmail.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. 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
C GG <cgg0007@gmail.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.
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