On Wed, May 10, 2017 at 3:06 AM, Petr Jelinek
wrote:
> Okay, then it's the same issue Masahiko Sawada reported in nearby
> thread, or at least has same cause.
This report is here:
https://www.postgresql.org/message-id/CAD21AoBYpyqTSw+=ES+xXtRGMPKh=pkiqjnxzknnuae0pst...@mail.gmail.com
It may be us
On 09/05/17 19:13, Jeff Janes wrote:
> On Tue, May 9, 2017 at 9:18 AM, Petr Jelinek
> mailto:petr.jeli...@2ndquadrant.com>> wrote:
>
> On 08/05/17 13:47, Petr Jelinek wrote:
> > On 08/05/17 01:17, Jeff Janes wrote:
> >> After dropping a subscription, it says it succeeded and that it dr
On Tue, May 9, 2017 at 9:18 AM, Petr Jelinek
wrote:
> On 08/05/17 13:47, Petr Jelinek wrote:
> > On 08/05/17 01:17, Jeff Janes wrote:
> >> After dropping a subscription, it says it succeeded and that it dropped
> >> the slot on the publisher.
> >>
> >> But the publisher still has the slot, and a
On 08/05/17 13:47, Petr Jelinek wrote:
> On 08/05/17 01:17, Jeff Janes wrote:
>> After dropping a subscription, it says it succeeded and that it dropped
>> the slot on the publisher.
>>
>> But the publisher still has the slot, and a full-tilt process described
>> by ps as
>>
>> postgres: wal sende
On 08/05/17 01:17, Jeff Janes wrote:
> After dropping a subscription, it says it succeeded and that it dropped
> the slot on the publisher.
>
> But the publisher still has the slot, and a full-tilt process described
> by ps as
>
> postgres: wal sender process jjanes [local] idle in transaction
>
After dropping a subscription, it says it succeeded and that it dropped the
slot on the publisher.
But the publisher still has the slot, and a full-tilt process described by
ps as
postgres: wal sender process jjanes [local] idle in transaction
Strace shows that this process is doing nothing but
