| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Evgeny Morozov <postgresql3(at)realityexists(dot)net> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: "PANIC: could not open critical system index 2662" - twice |
| Date: | 2023-05-16 23:39:50 |
| Message-ID: | 20230516233950.qk5ituuktdyo36bg@awork3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
On 2023-05-16 14:20:46 +0000, Evgeny Morozov wrote:
> On 9/05/2023 3:32 am, Andres Freund wrote:
> > Attached is a rough prototype of that idea (only using datconnlimit ==
> > -2 for now).
> > I guess we need to move this to -hackers. Perhaps I'll post subsequent
> > versions below
> > https://www.postgresql.org/message-id/20230314174521.74jl6ffqsee5mtug%40awork3.anarazel.de ?
> So now that a patch is in the works, can I drop the two corrupted
> databases?
Yes.
> Is there a workaround I can use to reduce the risk of running into this
> issue again until a patch is released? (Which I guess would be in August?)
Try to prevent the DROP DATABASE from getting cancelled :/. If you want to go
a bit further, you could rename the database to *_dropped before dropping it,
and then try to do the DROP DATABASE. That way you'd at least know that it's
corrupt because of a failed DROP database.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Avi Weinberg | 2023-05-17 06:05:52 | Postgres Incompatibility |
| Previous Message | Ron | 2023-05-16 21:36:45 | Re: Postresql HA 2 nodes |