Re: Logical replication launcher did not automatically restart when got SIGKILL - Mailing list pgsql-hackers

From cca5507
Subject Re: Logical replication launcher did not automatically restart when got SIGKILL
Date
Msg-id tencent_0423254B46018FF4A0D9CE30D4A510BCF605@qq.com
Whole thread Raw
In response to Re: Logical replication launcher did not automatically restart when got SIGKILL  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Logical replication launcher did not automatically restart when got SIGKILL
List pgsql-hackers
> For example, we could add a check like the following to 013_crash_restart.pl.
> Thoughts?

> -----------------
> is($node->safe_psql('postgres',
> "SELECT count(*) = 1 FROM pg_stat_activity WHERE backend_type =
> 'logical replication launcher'"),
> 't',
> 'logical replication launcher is running after crash');
> -----------------

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

--
Regards,
ChangAo Chen

pgsql-hackers by date:

Previous
From: Aidar Imamov
Date:
Subject: Re: HASH_FIXED_SIZE flag gets lost when attaching to existing hash table
Next
From: shveta malik
Date:
Subject: Re: Conflict detection for update_deleted in logical replication