| From: | Žiga Kranjec <ziga(at)ljudmila(dot)org> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: DROP SUBSCRIPTION with no slot |
| Date: | 2019-09-25 17:55:25 |
| Message-ID: | 648FD1C0-8D88-4693-A496-D0FC3DF6EFD0@ljudmila.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 25 Sep 2019, at 01:22, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
>
> There is no HINT in the error message itself, but there is in the documentation, see note at end of https://www.postgresql.org/docs/current/sql-dropsubscription.html <https://www.postgresql.org/docs/current/sql-dropsubscription.html>. I agree with you that the DROP should just work in this case, even more so than in my case. But if we go with the argument that doing that is too error prone, then do we want to include a HINT on how to be error prone more conveniently?
>
> Cheers,
>
> Jeff
Ah. I missed that bit in the documentation!
Perhaps a publication should remember, whether it actually created a replication slot and only try to remove it, if it did. Although that probably wouldn't help much in your case.
Ž.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Isaac Morland | 2019-09-25 18:41:53 | Re: DROP SUBSCRIPTION with no slot |
| Previous Message | Alvaro Herrera | 2019-09-25 17:48:12 | Re: Two pg_rewind patches (auto generate recovery conf and ensure clean shutdown) |