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

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Evgeny Morozov <postgresql3(at)realityexists(dot)net>
Cc: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: "PANIC: could not open critical system index 2662" - twice
Date: 2023-04-14 02:55:50
Message-ID: 8486f71f9c11e98af787e15e2d2ed0ecfdbf6ee7.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 2023-04-13 at 19:07 +0000, Evgeny Morozov wrote:
> On 13/04/2023 5:02 pm, Laurenz Albe wrote:
> > It means that if the error is caused by a faulty disk changing your data,
> > you'll notice as soon as you touch the page.
> >
> > That would perhaps not have made a lot of difference in your case,
> > except that the error message would have been different and proof
> > that the disk was the problem.
>
> OK, but we had data checksums on the whole time. So that means that the
> disk was NOT the problem in our case?

Hmm, I am not certain. The block was filled with zeros from your error
message, and I think such blocks don't trigger a checksum warning.
So if your disk replaces a valid block with zeros (filesystem check
after crash?), that could explain what you see.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thorsten Glaser 2023-04-14 04:00:22 Re: "PANIC: could not open critical system index 2662" - twice
Previous Message Bryn Llewellyn 2023-04-13 21:09:25 Re: Why does "fetch last from cur" always cause error 55000 for non-scrollable cursor?