| From: | Evgeny Morozov <postgresql3(at)realityexists(dot)net> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| 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 14:20:46 |
| Message-ID: | 0102018824ef5bc9-ac1d49a6-9928-44e8-bb65-df5154d418a5-000000@eu-west-1.amazonses.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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? 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?)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hubert depesz lubaczewski | 2023-05-16 14:23:02 | How can I change replication slot's restart_lsn from SQL? |
| Previous Message | Peter Eisentraut | 2023-05-16 13:12:19 | Re: function signature allow "default" keyword |