From: David Steele <david@pgbackrest.org>
To: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: Bug in recovery of drop database?
Date: Thu, 06 Feb 2025 15:55:21 +0000 (UTC)
Message-ID: <73f2e462-d767-4248-98ed-9c0fcdac10bf@pgbackrest.org> (raw)
In-Reply-To: <43f0c3df-a23c-4159-9610-934d3dceb80c@pgbackrest.org>
References: <43f0c3df-a23c-4159-9610-934d3dceb80c@pgbackrest.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: david@pgbackrest.org, pgsql-bugs@lists.postgresql.org
Subject: Re: Bug in recovery of drop database?
In-Reply-To: <73f2e462-d767-4248-98ed-9c0fcdac10bf@pgbackrest.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox