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

From: Evgeny Morozov <postgresql3(at)realityexists(dot)net>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: "PANIC: could not open critical system index 2662" - twice
Date: 2023-04-13 19:07:38
Message-ID: 010201877c0423c8-0a35b03c-d274-4857-ba99-ff7ea51d676b-000000@eu-west-1.amazonses.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bryn Llewellyn 2023-04-13 19:52:56 Why does "fetch last from cur" always cause error 55000 for non-scrollable cursor?
Previous Message Tom Lane 2023-04-13 17:30:05 Re: Unexpected behavior when combining `generated always` columns and update rules