Re: Logical WAL sender unresponsive during decoding commit

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Logical WAL sender unresponsive during decoding commit
Date: 2022-08-16 09:06:01
Message-ID: 162F1AF3-1D5E-4776-B7A2-F933A48C44A5@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 16 Aug 2022, at 10:25, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2022-08-16 09:06:39 Re: Logical WAL sender unresponsive during decoding commit
Previous Message Drouvot, Bertrand 2022-08-16 09:02:30 Re: [PATCH] Expose port->authn_id to extensions and triggers