Re:Re: BUG #17580: use pg_terminate_backend to terminate a wal senderprocess may wait a long time

Thanks!

I will upgrade our version after it is fixed to 10.

Regards,

--
Whale Song

Original Email

Sender:"Masahiko Sawada"< sawada(dot)mshk(at)gmail(dot)com &gt;;

Sent Time:2022/8/15 12:02

To:"WhaleSong"< 13207961(at)qq(dot)com &gt;;

Cc recipient:"pgsql-bugs"< pgsql-bugs(at)lists(dot)postgresql(dot)org &gt;;

Subject:Re: BUG #17580: use pg_terminate_backend to terminate a wal senderprocess may wait a long time

Hi,

On Mon, Aug 15, 2022 at 11:27 AM <13207961(at)qq(dot)com&gt; wrote:
&gt;
&gt; Hi Masahiko,
&gt; I think maybe you should use filter-tables to filter the test table, likes:
&gt; &nbsp; &nbsp; &nbsp; &nbsp;filter-tables="public.test666"
&gt;

Thanks, I could reproduce this issue with the option. And I've
confirmed this issue exists also in the latest minor version, 10.22,
and HEAD.

If the plugin filters out all changes, there is no place to check the
interruptions. So I think it makes sense to add CHECK_FOR_INTERRUPTS
to the main loop of processing logical change. It would be better to
do that on the core, rather than the plugin side. I've attached the
patch. I think we should backpatch to 10.

Regards,

--
Masahiko Sawada
EDB: &nbsp;https://www.enterprisedb.com/