Re: Logical WAL sender unresponsive during decoding commit - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Logical WAL sender unresponsive during decoding commit
Date
Msg-id CAA4eK1LLOTEF4KT8H5Sxg+A1su1c_OqEZLUbUZVyPP0b-g153w@mail.gmail.com
Whole thread Raw
In response to Logical WAL sender unresponsive during decoding commit  (Andrey Borodin <x4mmm@yandex-team.ru>)
Responses Re: Logical WAL sender unresponsive during decoding commit
List pgsql-hackers
On Tue, Aug 16, 2022 at 9:28 AM Andrey Borodin <x4mmm@yandex-team.ru> wrote:
>
> Hi hackers!
>
> Some time ago I've seen a hanging logical replication that was trying to send transaction commit after doing table
pg_repack.
> I understand that those things do not mix well. Yet walsender was ignoring pg_terminate_backend() and I think this
worthfixing.
 
> Can we add CHECK_FOR_INTERRUPTS(); somewhere in this backtrace?
>

I think if we want to do this in this code path then it may be it is
better to add it in ReorderBufferProcessTXN where we are looping to
process each change.

-- 
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Support logical replication of global object commands
Next
From: Andres Freund
Date:
Subject: Re: pg_upgrade test writes to source directory