| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Arseny Sher <a(dot)sher(at)postgrespro(dot)ru>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: DROP SUBSCRIPTION hangs if sub is disabled in the same transaction |
| Date: | 2017-09-13 13:56:15 |
| Message-ID: | 20170913135615.sxhwjp7bbo7bnq5g@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> > - Disallow DROP SUBSCRIPTION in a transaction under certain
> > circumstances, for example if a transaction has previously manipulated
> > the same subscription.
> ISTM the second of those (refuse to drop an in-use subscription) is
> by far the least surprising behavior.
+1 for that option. IIRC this has precedent for other object types such
as tables, where we refuse some action if we have already operated on
the table in the same transaction.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-09-13 14:11:23 | Re: psql: new help related to variables are not too readable |
| Previous Message | Jesper Pedersen | 2017-09-13 13:54:53 | Re: POC: Cache data in GetSnapshotData() |