| From: | "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: "PANIC: could not open critical system index 2662" - twice |
| Date: | 2023-04-07 14:10:20 |
| Message-ID: | 20230407141020.wysn6gnhb7sttl56@hjp.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2023-04-07 13:04:34 +0200, Laurenz Albe wrote:
> On Thu, 2023-04-06 at 16:41 +0000, Evgeny Morozov wrote:
> > What can I do to figure out why this is happening and prevent it from happening again?
>
> No idea about the former, but bad hardware is a good enough explanation.
>
> As to keeping it from happening: use good hardware.
Also: Use checksums. PostgreSQL offers data checksums[1]. Some filesystems
also offer checksums.
This doesn't prevent corruption but at least it will be detected early
and can't spread.
hp
[1] For some reason I thought the Debian/Ubuntu packages enabled this by
default. But that doesn't seem to be the case.
--
_ | Peter J. Holzer | Story must make more sense than reality.
|_|_) | |
| | | hjp(at)hjp(dot)at | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jehan-Guillaume de Rorthais | 2023-04-07 14:33:42 | Re: Patroni vs pgpool II |
| Previous Message | Tatsuo Ishii | 2023-04-07 12:16:04 | Re: Patroni vs pgpool II |