From: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> |
---|---|
To: | Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Fix doc of DROP SUBSCRIPTION |
Date: | 2017-06-30 15:24:27 |
Message-ID: | 8288b034-f90b-e6e5-f3ce-049c2b909c34@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 30/06/17 15:17, Yugo Nagata wrote:
> On Fri, 30 Jun 2017 20:17:39 +0900
> Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
>
>> On Fri, Jun 30, 2017 at 7:01 PM, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> wrote:
>>> Hi,
>>>
>>> The documentation says that a subscription that has a replication slot
>>> cannot be dropped in a transaction block, but it is not allowed even
>>> outside of a transaction block.
>>
>> Hmm, I think we can drop a subscription outside of a transaction block
>> even if the subscription associates with a replication.
>
> Sorry, I was wrong and missing something... I confirmaed it.
> The documentation is right. Sorry for the noise.
>
It will only fail if the remote site is not reachable during the drop
(but then it should hint about the ALTER), maybe that's what happened to
you?
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-06-30 15:26:38 | Re: CREATE COLLATION definitional questions for ICU |
Previous Message | Robert Haas | 2017-06-30 14:02:06 | Re: Small comment fix in partition.c |