Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, marko(at)joh(dot)to, pgsql-bugs(at)lists(dot)postgresql(dot)org, Magnus Hagander <magnus(at)hagander(dot)net>
Subject: Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot
Date: 2019-07-10 04:51:47
Message-ID: 20190710045147.GD1031@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Jul 09, 2019 at 05:46:30PM -0400, Alvaro Herrera wrote:
> Hmm ... so what that commit did is precisely to fix this bug.
> Magnus thought at the time he was fixing a pg10 bug,
> https://postgr.es/m/CABUevEwX4g8y=gmgfPzxFKS7gqjSYNR949Xc96OQm=YXJmh_Og@mail.gmail.com
> but apparently now we see that the bug was older than that. Maybe it's
> okay to backpatch further?

Yes, I would not be against a back-patch in this case. There is a
minor conflict because pre-9.6 WAL senders cannot run SQL queries but
that looks simple enough to solve.

> (Booh to missing "Discussion:" tags in commit messages)

Booh++
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Ishan joshi 2019-07-10 05:01:07 Re: BUG #15901: Tablespace showing as null in psql and pgadmin
Previous Message Peter Geoghegan 2019-07-10 03:06:50 Re: ERROR: found unexpected null value in index