On Tue, May 30, 2017 at 3:01 PM, Peter Eisentraut <peter.eisentr...@2ndquadrant.com> wrote: > On 5/25/17 17:26, Peter Eisentraut wrote: >> Another way to fix this particular issue is to not verify the >> replication slot name before doing the drop. After all, if the name is >> not valid, then you can also just report that it doesn't exist. > > Here is a possible patch along these lines.
I don't see how this solves the problem. Don't you still end up with an error message telling you that you can't drop the subscription, and no guidance as to how to fix it? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers