Re: "PANIC: could not open critical system index 2662" - twice - Mailing list pgsql-general

From Laurenz Albe
Subject Re: "PANIC: could not open critical system index 2662" - twice
Date
Msg-id a64bb8dcbe5e0e0775c81db43e61a773f355df09.camel@cybertec.at
Whole thread Raw
In response to Re: "PANIC: could not open critical system index 2662" - twice  (Evgeny Morozov <postgresql3@realityexists.net>)
Responses Re: "PANIC: could not open critical system index 2662" - twice  (Evgeny Morozov <postgresql3@realityexists.net>)
List pgsql-general
On Thu, 2023-05-04 at 15:49 +0000, Evgeny Morozov wrote:
> Well, the problem happened again! Kind of... This time PG has not
> crashed with the PANIC error in the subject, but pg_dumping certain DBs
> again fails with
>
>
> pg_dump: error: connection to server on socket
> "/var/run/postgresql/.s.PGSQL.5434" failed: FATAL:  index
> "pg_class_oid_index" contains unexpected zero page at block 0

If you dumped and restored the database after the last time the error
happened, there must be a systemic problem.

Perhaps you have bad hardware, or a problem with a storage driver,
file system or some other low-level software component.
It might of course be a PostgreSQL bug too, but it is hard to say
without a way to reproduce...

Yours,
Laurenz Albe



pgsql-general by date:

Previous
From: Evgeny Morozov
Date:
Subject: Re: "PANIC: could not open critical system index 2662" - twice
Next
From: Evgeny Morozov
Date:
Subject: Re: "PANIC: could not open critical system index 2662" - twice