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

From: cca5507 <cca5507(at)qq(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, 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-25 13:53:00
Message-ID: tencent_0423254B46018FF4A0D9CE30D4A510BCF605@qq.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2025-07-25 13:54:25 Re: Conflict detection for update_deleted in logical replication
Previous Message Aidar Imamov 2025-07-25 13:37:48 Re: HASH_FIXED_SIZE flag gets lost when attaching to existing hash table