| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Evgeny Morozov <postgresql3(at)realityexists(dot)net> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Alban Hertroys <haramrae(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: "PANIC: could not open critical system index 2662" - twice |
| Date: | 2023-05-05 00:02:10 |
| Message-ID: | CA+hUKGLwDBnVHbef=p-BonSfiU1-XRoEg3ShECRZJFx2ti=TuQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, May 5, 2023 at 11:15 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> What does select
> pg_relation_filepath('pg_class_oid_index') show in the corrupted
> database, base/5/2662 or something else?
Oh, you can't get that far, but perhaps you could share the
pg_filenode.map file? Or alternatively strace -f PostgreSQL while
it's starting up to see which file it's reading, just to be sure. One
way to find clues about whether PostgreSQL did something wrong, once
we definitely have the right relfilenode for the index, aside from
examining its contents, would be to search the WAL for references to
that block with pg_waldump. Maybe you still have enough WAL if it
happened recently?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wen Yi | 2023-05-05 01:00:37 | What type of Compiler to SQL? Memory-Image (Load-and-Go) Format? |
| Previous Message | Thomas Munro | 2023-05-04 23:27:38 | Re: "PANIC: could not open critical system index 2662" - twice |