Re: [HACKERS] Better error message for trying to drop a DB with open subscriptions? - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: [HACKERS] Better error message for trying to drop a DB with open subscriptions?
Date
Msg-id CAMkU=1xqtFhJG+J-NrAfZAXW1fmqwqP0YMGXZXgCb+_Sf20epQ@mail.gmail.com
Whole thread Raw
In response to [HACKERS] Better error message for trying to drop a DB with open subscriptions?  (Josh Berkus <josh@berkus.org>)
List pgsql-hackers
On Thu, Jul 20, 2017 at 4:09 PM, Josh Berkus <josh@berkus.org> wrote:
All:

The problem:

postgres=# drop database bookdata;
ERROR:  database "bookdata" is being accessed by other users
DETAIL:  There is 1 other session using the database.
postgres=# \c bookdata
You are now connected to database "bookdata" as user "postgres".
bookdata=# drop subscription wholedb;
NOTICE:  dropped replication slot "wholedb" on publisher
DROP SUBSCRIPTION
bookdata=# \c postgres
You are now connected to database "postgres" as user "postgres".
postgres=# drop database bookdata;
DROP DATABASE

Is there any easy way for us to detect that the "user" accessing the
target database is actually a logical replication subscription, and give
the DBA a better error message (e.g. "database 'bookdata' still has open
subscrptions")?


+1

Better yet would be to just cascade the drop, but I assume that would be harder to do.

Cheers,

Jeff

pgsql-hackers by date:

Previous
From: Mark Kirkwood
Date:
Subject: Re: [HACKERS] autovacuum can't keep up, bloat just continues to rise
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: [HACKERS] PgFDW connection invalidation by ALTER SERVER/ALTERUSER MAPPING