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

From Tom Lane
Subject Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot
Date
Msg-id 21922.1562852647@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #15888: Bogus "idle in transaction" state for logicaldecoding client after creating a slot  (Magnus Hagander <magnus@hagander.net>)
Responses Re: BUG #15888: Bogus "idle in transaction" state for logicaldecoding client after creating a slot  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
Magnus Hagander <magnus@hagander.net> writes:
> We've tried that once, and I think even twice, and failed miserably at any
> form of agreement. But we could certainly try again :)

I thought we *did* have an agreement, to wit using

Discussion: https://postgr.es/m/<message-id>

to link to relevant mail thread(s).  Some people use more tags
but that seems inessential to me.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #15888: Bogus "idle in transaction" state for logicaldecoding client after creating a slot
Next
From: "David G. Johnston"
Date:
Subject: Re: The result of the pattern matching is incorrect when the patternstring is bpchar type