| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | shveta malik <shveta(dot)malik(at)gmail(dot)com>, cca5507 <cca5507(at)qq(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Logical replication launcher did not automatically restart when got SIGKILL |
| Date: | 2025-07-15 15:20:05 |
| Message-ID: | fe865941-16f6-47dd-8a8b-f2fe71c5e4ec@oss.nttdata.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| 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(at)qq(dot)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(at)mail(dot)gmail(dot)com
[2] https://commitfest.postgresql.org/patch/5844/
--
Fujii Masao
NTT DATA Japan Corporation
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2025-07-15 15:50:17 | Re: Interrupts vs signals |
| Previous Message | Dean Rasheed | 2025-07-15 15:14:44 | Re: small fix for pg_overexplain docs |