From: 巨鲸 <13207961@qq.com>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re:Re: BUG #17580: use pg_terminate_backend to terminate a wal senderprocess may wait a long time
Date: Tue, 16 Aug 2022 11:26:12 +0800
Message-ID: <tencent_8FF2C8F52B54DD943BAEC625E6A868756806@qq.com> (raw)
Thanks!
I will upgrade our version after it is fixed to 10.
Regards,
--
Whale Song
Original Email
Sender:"Masahiko Sawada"< sawada.mshk@gmail.com >;
Sent Time:2022/8/15 12:02
To:"WhaleSong"< 13207961@qq.com >;
Cc recipient:"pgsql-bugs"< pgsql-bugs@lists.postgresql.org >;
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@qq.com> wrote:
>
> Hi Masahiko,
> I think maybe you should use filter-tables to filter the test table, likes:
> filter-tables="public.test666"
>
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: https://www.enterprisedb.com/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: 13207961@qq.com, sawada.mshk@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re:Re: BUG #17580: use pg_terminate_backend to terminate a wal senderprocess may wait a long time
In-Reply-To: <tencent_8FF2C8F52B54DD943BAEC625E6A868756806@qq.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox