Re: DROP SUBSCRIPTION, query cancellations and slot handling

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: 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 12:41:25
Message-ID: CAB7nPqQ6fwMgGMaerttJPSy-_DYnZR4M2mU69f5Y9Ph=YZLW8w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 20, 2017 at 8:47 PM, Petr Jelinek
<petr(dot)jelinek(at)2ndquadrant(dot)com> wrote:
> Or you can drop the slot manually on upstream.

Sure, but the point here is that if for example users have
client_min_messages set at least at warning, they may have no idea
that an underlying slot has been created. This is a confusing
experience for users.

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.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nikolay Shaplov 2017-04-20 12:48:16 Re: pgbench tap tests & minor fixes
Previous Message Petr Jelinek 2017-04-20 11:52:05 Re: logical replication and PANIC during shutdown checkpoint in publisher