Re: Fix LOCK_TIMEOUT handling in slotsync worker - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Fix LOCK_TIMEOUT handling in slotsync worker
Date
Msg-id CAA4eK1JjO0dtFk+GH37TsSVd4pkFwmm=j5rd0UEPDnBJSuOo_Q@mail.gmail.com
Whole thread Raw
In response to Re: Fix LOCK_TIMEOUT handling in slotsync worker  (Chao Li <li.evan.chao@gmail.com>)
Responses Re: Fix LOCK_TIMEOUT handling in slotsync worker
RE: Fix LOCK_TIMEOUT handling in slotsync worker
List pgsql-hackers
On Mon, Dec 8, 2025 at 1:06 PM Chao Li <li.evan.chao@gmail.com> wrote:
>
> I have nit comment:
>
> ```
> -       if (ShutdownRequestPending)
> +       if (SlotSyncCtx->stopSignaled)
>         {
>                 ereport(LOG,
> -                               errmsg("replication slot synchronization worker is shutting down on receiving
SIGINT"));
> +                               errmsg("replication slot synchronization worker is shutting down because promotion is
triggered"));
> ```
>
> In the error message, “because promotion is triggered" sound a little redundant, can be just:
>
> "replication slot synchronization worker is shutting down due to promotion"
>

We have a number of existing similar messages like:  "logical
replication parallel apply worker for subscription \"%s\" will stop
because of a parameter change". So, how about: "replication slot
synchronization worker will stop because promotion is triggered"?

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: add some errhint for regexp* functions.
Next
From: Nico Williams
Date:
Subject: Re: [Patch] Add WHERE clause support to REFRESH MATERIALIZED VIEW