From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Simone Gotti <simone(dot)gotti(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] Fix drop replication slot blocking instead of returning error |
Date: | 2017-08-29 14:02:59 |
Message-ID: | 20170829140259.amlbheprd6juajbb@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2017-08-29 13:42:05 +0200, Simone Gotti wrote:
> On Tue, Aug 29, 2017 at 12:13 PM, Alvaro Herrera
> <alvherre(at)2ndquadrant(dot)com> wrote:
> >
>
> Hi Alvaro,
>
> > Simone Gotti wrote:
> > > Hi all,
> > >
> > > I noticed that in postgres 10beta3, calling pg_drop_replication_slot on an
> > > active slot will block until it's released instead of returning an error
> > > like
> > > done in pg 9.6. Since this is a change in the previous behavior and the docs
> > > wasn't changed I made a patch to restore the previous behavior.
> >
> > Changing that behavior was the entire point of the cited commit.
>
> Sorry, I was thinking that the new behavior was needed for internal
> future functions since the doc wasn't changed.
FWIW, I also don't think it's ok to just change the behaviour
unconditionally and without a replacement for existing behaviour.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-08-29 15:21:33 | Re: Explicit relation name in VACUUM VERBOSE log |
Previous Message | David Steele | 2017-08-29 13:59:46 | Re: Update low-level backup documentation to match actual behavior |