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

On Wed, Jul 16, 2025 at 8:51 AM cca5507 <cca5507@qq.com> wrote:
>
> Hi,
>
> The v1-0002 in [1] will call ReportBackgroundWorkerExit() which will send SIGUSR1 to 'bgw_notify_pid', but it may
alreadyexit in HandleChildCrash(), is this ok? 
>

Shall ReportBackgroundWorkerExit() be skipped for 'crashed' background worker?

If we look at code prior to commit 28a520c0b77, there we were setting
'rw_crashed_at' in CleanupBackgroundWorker() and then
HandleChildCrash() was resetting the pid and exiting with no
additional processing.

thanks
Shveta