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

From: shveta malik <shveta(dot)malik(at)gmail(dot)com>
To: cca5507 <cca5507(at)qq(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, shveta malik <shveta(dot)malik(at)gmail(dot)com>
Subject: Re: Logical replication launcher did not automatically restart when got SIGKILL
Date: 2025-07-17 09:57:41
Message-ID: CAJpy0uCe-ns-H-7c4SM9+7xvzUoZZUZhpzGAjuXBnQKfa9pWAg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 16, 2025 at 8:51 AM cca5507 <cca5507(at)qq(dot)com> wrote:
>
> 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?
>

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mahendra Singh Thalor 2025-07-17 10:16:41 Re: Non-text mode for pg_dumpall
Previous Message Amit Kapila 2025-07-17 09:37:42 Re: POC: enable logical decoding when wal_level = 'replica' without a server restart