Re: Logical replication launcher did not automatically restart when got SIGKILL - Mailing list pgsql-hackers

From cca5507
Subject Re: Logical replication launcher did not automatically restart when got SIGKILL
Date
Msg-id tencent_82856A635246657EF0500EECEC2E42590A09@qq.com
Whole thread Raw
In response to Re: Logical replication launcher did not automatically restart when got SIGKILL  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List 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

pgsql-hackers by date:

Previous
From: Ajin Cherian
Date:
Subject: Re: 024_add_drop_pub.pl might fail due to deadlock
Next
From: Fujii Masao
Date:
Subject: Re: Log prefix missing for subscriber log messages received from publisher