Re: "PANIC: could not open critical system index 2662" - twice

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: Evgeny Morozov <postgresql3(at)realityexists(dot)net>, PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: "PANIC: could not open critical system index 2662" - twice
Date: 2023-04-07 11:31:45
Message-ID: ZC//IebyxtiHMymO@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Apr 07, 2023 at 01:04:34PM +0200, Laurenz Albe wrote:
> On Thu, 2023-04-06 at 16:41 +0000, Evgeny Morozov wrote:
>> Could this be a PG bug?
>
> It could be, but data corruption caused by bad hardware is much more likely.

There is no way to be completely sure here, except if we would be able
to put our hands on a reproducible test case that would break the
cluster so much that we'd get into this state. I don't recall seeing
this error pattern in recent history, though.
--
Michael

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tatsuo Ishii 2023-04-07 12:10:42 Re: Patroni vs pgpool II
Previous Message Ron 2023-04-07 11:12:22 Re: Patroni vs pgpool II