Horton
Menu

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

Laurenz Albe <laurenz.albe@cybertec.at>

View thread
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Evgeny Morozov <postgresql3@realityexists.net>, Michael Paquier <michael@paquier.xyz>
Cc: PostgreSQL General <pgsql-general@postgresql.org>, "Peter J. Holzer" <hjp-pgsql@hjp.at>
Date: 2023-04-13T15:02:11Z
Lists: 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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Handle DROP DATABASE getting interrupted

  2. Remove the restriction that the relmap must be 512 bytes.