Andres Freund <andres@anarazel.de> writes:
> I was just writing a test to verify that the slot / stats bug you just
> encountered is / stays fixed. I ended up doing it in isolationtester, because
> that was the easiest to get reliable. When terminating an isolationtester
> connection, I see the FATAL twice in isolationtester output:
Yeah, see
https://www.postgresql.org/message-id/flat/ab4288f8-be5c-57fb-2400-e3e857f53e46%40enterprisedb.com
I haven't thought of a way to get rid of that that I like.
(There's a cleanup proposal in that thread that I've not
yet implemented, but it won't do anything for connection-loss
cases, I think.)
regards, tom lane