| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Evgeny Morozov <postgresql3(at)realityexists(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org>, "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at> |
| Subject: | Re: "PANIC: could not open critical system index 2662" - twice |
| Date: | 2023-04-13 15:02:11 |
| Message-ID: | c6a6f6c7a3e9a707ac7b28cefeca67d045ecc63a.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2023-04-13 15:07:09 | Re: JSON / ASP.NET AJAX Dates support in PostgreSQL |
| Previous Message | Sebastien Flaesch | 2023-04-13 14:44:45 | JSON / ASP.NET AJAX Dates support in PostgreSQL |