Re: Logical replication launcher did not automatically restart when got SIGKILL

From: cca5507 <cca5507(at)qq(dot)com>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Logical replication launcher did not automatically restart when got SIGKILL
Date: 2025-07-16 03:21:10
Message-ID: tencent_82856A635246657EF0500EECEC2E42590A09@qq.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

The v1-0002 in [1] will call ReportBackgroundWorkerExit() which will send SIGUSR1 to 'bgw_notify_pid', but it may already exit in HandleChildCrash(), is this ok?

[1]
https://commitfest.postgresql.org/patch/5844/

--
Regards,
ChangAo Chen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-07-16 03:39:00 Re: Log prefix missing for subscriber log messages received from publisher
Previous Message Ajin Cherian 2025-07-16 03:08:04 Re: 024_add_drop_pub.pl might fail due to deadlock