| From: | David Steele <david(at)pgbackrest(dot)org> |
|---|---|
| To: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Bug in recovery of drop database? |
| Date: | 2025-02-06 15:55:21 |
| Message-ID: | 73f2e462-d767-4248-98ed-9c0fcdac10bf@pgbackrest.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2/5/25 15:24, David Steele wrote:
>
> psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed:
> FATAL: cannot connect to invalid database "mytest"
> HINT: Use DROP DATABASE to drop invalid databases.
Since this error message started cropping up fairly recently I had a
look at related commits and found this:
c66a7d75 Handle DROP DATABASE getting interrupted
This commit changed the error message so it is more obvious that
something has gone wrong, but the underlying issue appears the same for
recovery.
Before c66a7d75 it looked like this:
FATAL: database "mytest" does not exist
DETAIL: The database subdirectory "base/16384" is missing.
Which seems reasonable when just looking at the error and not the detail.
Regards,
-David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2025-02-06 18:05:31 | Re: Bug in recovery of drop database? |
| Previous Message | Tom Lane | 2025-02-06 15:26:02 | Re: BUG #18799: /src/interfaces/ecpg/pgtypeslib/timestamp.c possible NULL deref |