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

From: Evgeny Morozov <postgresql3(at)realityexists(dot)net>
To: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Cc: Thomas Munro <thomas(dot)munro(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 09:12:01
Message-ID: 01020187eb2ebb95-bce9827e-141b-4f45-865c-3edc61e3d830-000000@eu-west-1.amazonses.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 5/05/2023 10:38 am, Andrew Gierth wrote:
> sudo -u postgres psql -w -p 5434 -d "options='-P'"
> (make that -d "dbname=whatever options='-P'" if you need to specify
> some database name; or use PGOPTIONS="-P" in the environment.)

Thanks, good to know! Unfortunately that also fails:

# sudo -u postgres psql -w -p 5434 -d
"dbname=test_behavior_638186279733138190 options='-P'"
psql: error: connection to server on socket
"/var/run/postgresql/.s.PGSQL.5434" failed: FATAL:  could not open
relation with OID 2964

(PG server log contains the same error message and no further details.)

select 2964::regclass returns "pg_db_role_setting" FWIW.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter Smith 2023-05-05 10:09:33 Re: Support logical replication of DDLs
Previous Message Magnus Hagander 2023-05-05 08:38:50 Re: connecting to localhost -> ::1 client_addr ?