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

cca5507 <cca5507@qq.com>

From: cca5507 <cca5507@qq.com>

To: Fujii Masao <masao.fujii@oss.nttdata.com>, shveta malik <shveta.malik@gmail.com>

Cc: pgsql-hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-07-16T03:21:10Z

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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Add regression test for background worker restart after crash.
- cc321b1d1c55 19 (unreleased) landed
Fix background worker not restarting after crash-and-restart cycle.
- 75f633f54aaa 18.0 landed
- b5d084c5353f 19 (unreleased) landed
Refactor code to handle death of a backend or bgworker in postmaster
- 28a520c0b773 18.0 cited