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

On 5/05/2023 2:02 am, Thomas Munro wrote:
> 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?

Hi Thomas, thanks very much for looking into this!

Indeed, I cannot get that far due to the same error. I read about
ignore_system_indexes, but...

# sudo -u postgres psql -w -p 5434 -c "set ignore_system_indexes=on";
ERROR:  parameter "ignore_system_indexes" cannot be set after connection
start

I'm not sure how to set it BEFORE connection start, but without
restarting the server (which I'd rather avoid if I can).

The OID of the bad DB ('test_behavior_638186279733138190') is 1414389
and I've uploaded base/1414389/pg_filenode.map and also base/5/2662 (in
case that's helpful) as
https://objective.realityexists.net/temp/pgstuff1.zip

> Maybe you still have enough WAL if it happened recently?

Maybe! What should I do with pg_waldump? I've never used it before.