Hi,
On 2022-02-14 19:48:00 -0500, Tom Lane wrote:
> 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
Ah, thanks.
Is the generation of the duplicated error message reliable in case of a
pg_terminate_backend()? Kinda looks like it should be?
I guess I'll push the fix without a test for now...
Greetings,
Andres Freund