Re: Bug in recovery of drop database? - Mailing list pgsql-bugs

From David Steele
Subject Re: Bug in recovery of drop database?
Date
Msg-id 73f2e462-d767-4248-98ed-9c0fcdac10bf@pgbackrest.org
Whole thread Raw
In response to Bug in recovery of drop database?  (David Steele <david@pgbackrest.org>)
List 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



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #18799: /src/interfaces/ecpg/pgtypeslib/timestamp.c possible NULL deref
Next
From: David Steele
Date:
Subject: Re: Bug in recovery of drop database?