Downloads
Home   >   mailing lists

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

From shveta malik
Subject Re: Logical replication launcher did not automatically restart when got SIGKILL
Date
Msg-id CAJpy0uCe-ns-H-7c4SM9+7xvzUoZZUZhpzGAjuXBnQKfa9pWAg@mail.gmail.com
Whole thread Raw
In response to Re: Logical replication launcher did not automatically restart when got SIGKILL  ("cca5507" <cca5507@qq.com>)
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: POC: enable logical decoding when wal_level = 'replica' without a server restart
Next
From: Mahendra Singh Thalor
Date:
Subject: Re: Non-text mode for pg_dumpall