| 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-09 01:32:55 |
| Message-ID: | 20230509013255.fjrlpitnj3ltur76@awork3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
On 2023-05-08 17:46:37 -0700, Andres Freund wrote:
> My current gut feeling is that we should use datconnlimit == -2 to prevent
> connections after reaching DropDatabaseBuffers() in dropdb(), and use a new
> column in 16, for both createdb() and dropdb().
Attached is a rough prototype of that idea (only using datconnlimit == -2 for
now).
This would need a fair bit more polish. The tests are crappy and output stuff
to stderr and don't validate enough. The error messages are bad. No docs
changes. More comments about why datconnlimit == -2 is used. Etc.
But I think it should be sufficient to discuss whether this is a viable path.
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 ?
Greetings,
Andres Freund
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Handle-interrupted-DROP-DATABASE.patch | text/x-diff | 7.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2023-05-09 04:03:59 | Re: "PANIC: could not open critical system index 2662" - twice |
| Previous Message | Andres Freund | 2023-05-09 00:46:37 | Re: "PANIC: could not open critical system index 2662" - twice |