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

Evgeny Morozov <postgresql3@realityexists.net>

From: Evgeny Morozov <postgresql3@realityexists.net>
To: Andrew Gierth <andrew@tao11.riddles.org.uk>
Cc: Thomas Munro <thomas.munro@gmail.com>, PostgreSQL General <pgsql-general@postgresql.org>
Date: 2023-05-05T09:12:01Z
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.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Handle DROP DATABASE getting interrupted

  2. Remove the restriction that the relmap must be 512 bytes.