Horton
Menu

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

cca5507 <cca5507@qq.com>

View thread
From: cca5507 <cca5507@qq.com>
To: Fujii Masao <masao.fujii@gmail.com>, shveta malik <shveta.malik@gmail.com>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-07-25T13:53:00Z
Lists: pgsql-hackers 
&gt; For example, we could add a check like the following to 013_crash_restart.pl.
&gt; Thoughts?
&gt;&nbsp;
&gt; -----------------
&gt; is($node-&gt;safe_psql('postgres',
&gt; "SELECT count(*) = 1 FROM pg_stat_activity WHERE backend_type =
&gt; 'logical replication launcher'"),
&gt; 't',
&gt; 'logical replication launcher is running after crash');
&gt; -----------------


Agree, but we need note that the logical replication launcher won't be registered in some case. (see ApplyLauncherRegister())


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

  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