| From: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
|---|---|
| To: | Žiga Kranjec <ziga(at)ljudmila(dot)org> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, 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 18:41:53 |
| Message-ID: | CAMsGm5fx5821uhBgEKDtt8mJv5JAYf22uVv-XtKrxuO1BCohpg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 25 Sep 2019 at 13:55, Žiga Kranjec <ziga(at)ljudmila(dot)org> wrote:
>
> 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.
>
What about issuing a NOTICE if the slot doesn't exist? I'm thinking if it
is able to connect to the primary and issue the command to delete the slot,
but it doesn't exist, not in case of arbitrary errors. I believe there is
precedent for similar behaviour from all the DROP ... IF EXISTS commands.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ahsan Hadi | 2019-09-25 18:46:28 | Re: Proposal for syntax to support creation of partition tables when creating parent table |
| Previous Message | Žiga Kranjec | 2019-09-25 17:55:25 | Re: DROP SUBSCRIPTION with no slot |