Horton
Menu

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

Evgeny Morozov <postgresql3@realityexists.net>

View thread
From: Evgeny Morozov <postgresql3@realityexists.net>
To: Andres Freund <andres@anarazel.de>
Cc: PostgreSQL General <pgsql-general@postgresql.org>
Date: 2023-05-09T07:40:35Z
Lists: pgsql-general 
On 8/05/2023 11:04 pm, Andres Freund wrote:
> Are you using any extensions?

Only plpgsql.

> Do you have any chance to figure out what statements were running
> concurrently with the DROP DATABASE?
No. Is there some way to log that, other than just logging all
statements (which seems impractical)? Most of the statements running on
that server should be inserts into another database, some reads.
Something could be creating or dropping partitions in another DB in
parallel, too, but not frequently.

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.