Re: Logical WAL sender unresponsive during decoding commit
x4mmm@yandex-team.ru
From: Andrey Borodin <x4mmm@yandex-team.ru>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2022-08-16T09:06:01Z
Lists: pgsql-hackers
> On 16 Aug 2022, at 10:25, Masahiko Sawada <sawada.mshk@gmail.com> wrote: > > The same issue is recently reported[1] on -bugs Oh, I missed that thread. > and I proposed the > patch that adds CHECK_FOR_INTERRUPTS() to the loop in > ReorderBufferProcessTXN(). I agree that it's a good place for check. > I think it should be backpatched. Yes, I think so too. > [1] https://www.postgresql.org/message-id/CAD21AoD%2BaNfLje%2B9JOqWbTiq1GL4BOp9_f7FxLADm8rS8cDhCQ%40mail.gmail.com The patch in this thread looks good to me. Thank you! Best regards, Andrey Borodin.
Commits
-
Add CHECK_FOR_INTERRUPTS while restoring changes during decoding.
- ce20f8b9f435 16.0 landed
- 10eaa975018f 15.1 landed
- 36fc013fabd9 14.6 landed
- 1eed947f9852 13.9 landed
- f7f82cf05a3f 12.13 landed
- 5c51afe23d65 11.18 landed
- 61838d2dd3c4 10.23 landed
-
Add CHECK_FOR_INTERRUPTS while decoding changes.
- f972ec5c285c 16.0 landed
- 42681dffafa2 15.0 landed
- 6d05d575bec5 14.6 landed
- 4985a45917c8 13.9 landed
- 9415873aee9d 12.13 landed
- 51e9469a41ad 11.18 landed
- 6b50433e865e 10.23 landed