Re: BUG #15888: Bogus "idle in transaction" state for logicaldecoding client after creating a slot - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #15888: Bogus "idle in transaction" state for logicaldecoding client after creating a slot
Date
Msg-id 20190710045147.GD1031@paquier.xyz
Whole thread Raw
In response to Re: BUG #15888: Bogus "idle in transaction" state for logicaldecoding client after creating a slot  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: BUG #15888: Bogus "idle in transaction" state for logicaldecoding client after creating a slot  (Andres Freund <andres@anarazel.de>)
List 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

Attachment

pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: ERROR: found unexpected null value in index
Next
From: Ishan joshi
Date:
Subject: Re: BUG #15901: Tablespace showing as null in psql and pgadmin