| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Evgeny Morozov <postgresql3(at)realityexists(dot)net>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: "PANIC: could not open critical system index 2662" - twice |
| Date: | 2023-05-08 02:46:37 |
| Message-ID: | CA+hUKG+wCOQzgLpWUrUvx_4SPUaeKC-ZK5mUwqP2G482syJyJw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, May 8, 2023 at 2:24 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> I can reproduce the same backtrace here. That's just my usual laptop
> with ext4, so this would be a Postgres bug. First, here are the four
> things running in parallel so as I can get a failure in loading a
> critical index when connecting:
That sounds like good news, but I'm still confused: do you see all 0s
in the target database (popo)'s catalogs, as reported (and if so can
you explain how they got there?), or is it regression that is
corrupted in more subtle ways also involving 1s?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2023-05-08 06:20:03 | Re: "PANIC: could not open critical system index 2662" - twice |
| Previous Message | Michael Paquier | 2023-05-08 02:24:48 | Re: "PANIC: could not open critical system index 2662" - twice |