| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Evgeny Morozov <postgresql3(at)realityexists(dot)net>, Alban Hertroys <haramrae(at)gmail(dot)com> |
| Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: "PANIC: could not open critical system index 2662" - twice |
| Date: | 2023-05-04 16:42:34 |
| Message-ID: | a64bb8dcbe5e0e0775c81db43e61a773f355df09.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Evgeny Morozov | 2023-05-04 18:10:49 | Re: "PANIC: could not open critical system index 2662" - twice |
| Previous Message | Evgeny Morozov | 2023-05-04 15:49:03 | Re: "PANIC: could not open critical system index 2662" - twice |