Horton
Menu

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

Fujii Masao <masao.fujii@oss.nttdata.com>

View thread
From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: shveta malik <shveta.malik@gmail.com>, cca5507 <cca5507@qq.com>
Cc: pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-07-15T15:20:05Z
Lists: pgsql-hackers 

On 2025/07/16 0:08, Fujii Masao wrote:
> 
> 
> On 2025/07/15 19:34, shveta malik wrote:
>> On Tue, Jul 15, 2025 at 2:56 PM cca5507 <cca5507@qq.com> wrote:
>>>
>>> Hi, hackers
>>>
>>> I found the $SUBJECT, the main reason is that RegisteredBgWorker::rw_pid has not been cleaned.
>>>
>>> Attach a patch to fix it.
> 
> Thanks for the report!
> 
> This issue appears to have been introduced by commit 28a520c0b77. As a result,
> not only the logical replication launcher but also other background workers
> (like autoprewarm) may fail to restart after a server crash.

I found that the same issue was previously reported here [1],
and a patch has been added to the current commitfest [2].

Regards,

[1] https://www.postgresql.org/message-id/flat/CAF6JsWiO=i24qYitWe6ns1sXqcL86rYxdyU+pNYk-WueKPSySg@mail.gmail.com
[2] https://commitfest.postgresql.org/patch/5844/

-- 
Fujii Masao
NTT DATA Japan Corporation

Commits

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

  1. Add regression test for background worker restart after crash.

  2. Fix background worker not restarting after crash-and-restart cycle.

  3. Refactor code to handle death of a backend or bgworker in postmaster