Logical replication launcher did not automatically restart when got SIGKILL

cca5507 <cca5507@qq.com>

From: cca5507 <cca5507@qq.com>

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

Date: 2025-07-15T09:25:58Z

Lists: pgsql-hackers

Attachments

v1-0001-logical-replication-launcher-did-not-automaticall.patch (application/octet-stream) patch v1-0001

Hi, hackers


I found the $SUBJECT, the main reason is that RegisteredBgWorker::rw_pid has not been cleaned.


Attach a patch to fix it.


--
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