| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> | 
|---|---|
| To: | Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> | 
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: Fix doc of DROP SUBSCRIPTION | 
| Date: | 2017-06-30 11:17:39 | 
| Message-ID: | CAD21AoCTL5=vqqTF1uOsf9nvqKx06a0fGUiQa0wLwC6AQ_svBw@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
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.
=# table pg_subscription;
 subdbid | subname  | subowner | subenabled |        subconninfo
 | subslotname | subsynccommit | subpublications
---------+----------+----------+------------+---------------------------+-------------+---------------+-----------------
   13164 | hoge_sub |       10 | t          | dbname=postgres
port=5550 | hoge_sub    | off           | {one_pub}
(1 row)
=# drop subscription hoge_sub ;
DROP SUBSCRIPTION
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2017-06-30 12:10:03 | Re: [HACKERS] Postgres process invoking exit resulting in sh-QUIT core | 
| Previous Message | Yugo Nagata | 2017-06-30 10:01:20 | Fix doc of DROP SUBSCRIPTION |