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 c6a6f6c7a3e9a707ac7b28cefeca67d045ecc63a.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
List pgsql-general
On Thu, 2023-04-13 at 06:56 +0000, Evgeny Morozov wrote:
> On 12/04/2023 2:35 am, Michael Paquier wrote:
> > initdb does not enable checksums by default, requiring a
> > -k/--data-checksums, so likely this addition comes from from your
> > environment.
>
> OK, so then what does that mean for the error in the subject? At what
> point should that problem have been detected by the data checksums?

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.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com



pgsql-general by date:

Previous
From: Sebastien Flaesch
Date:
Subject: JSON / ASP.NET AJAX Dates support in PostgreSQL
Next
From: Ron
Date:
Subject: Re: JSON / ASP.NET AJAX Dates support in PostgreSQL