| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: DROP SUBSCRIPTION, query cancellations and slot handling |
| Date: | 2017-04-20 21:25:07 |
| Message-ID: | 1edf7681-9ac6-3e26-d03e-22ae3d6c0b30@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/20/17 08:41, Michael Paquier wrote:
> As subscription is a self-contained concept, it seems to me that any
> errors happening should at least try to do some cleanup action before
> just giving up processing, that would be a less frustrating
> experience.
This is the way it's designed.
The alternative is to do what we currently do for physical replication,
namely requiring the user to set up all the replication slots manually
beforehand. I don't think that's a better experience. There was a
thread about having pg_basebackup automatically create replication
slots. That will have to deal with the same issues.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-04-20 21:27:42 | Re: Removing select(2) based latch (was Unportable implementation of background worker start) |
| Previous Message | Alvaro Herrera | 2017-04-20 21:24:26 | WITH clause in CREATE STATISTICS |