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

Поиск
Список
Период
Сортировка
От Masahiko Sawada
Тема Re: BUG #17580: use pg_terminate_backend to terminate a wal sender process may wait a long time
Дата
Msg-id CAD21AoD+aNfLje+9JOqWbTiq1GL4BOp9_f7FxLADm8rS8cDhCQ@mail.gmail.com
обсуждение исходный текст
Ответ на BUG #17580: use pg_terminate_backend to terminate a wal sender process may wait a long time  (PG Bug reporting form <noreply@postgresql.org>)
Ответы Re: BUG #17580: use pg_terminate_backend to terminate a wal sender process may wait a long time  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Список pgsql-bugs
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/

Вложения

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Peter Smith
Дата:
Сообщение: Re: No-op updates with partitioning and logical replication started failing in version 13
Следующее
От: "houzj.fnst@fujitsu.com"
Дата:
Сообщение: RE: No-op updates with partitioning and logical replication started failing in version 13