Hi,
On 2022-02-12 16:56:38 -0500, Tom Lane wrote:
> I went ahead and pushed the patches-under-discussion (the larger
> one only to HEAD, for now).
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:
step s2_init: SELECT 'init' FROM pg_create_logical_replication_slot('slot_create_error', 'test_decoding'); <waiting
...>
step s1_terminate_s2:
SELECT pg_terminate_backend(pid) FROM pg_stat_activity WHERE application_name = 'isolation/error/s2';
pg_terminate_backend
--------------------
t
(1 row)
step s2_init: <... completed>
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
I haven't yet tracked down whether that's related to these changes, but I
thought it was interesting enough to bring up...
Greetings,
Andres Freund