Re: Fix LOCK_TIMEOUT handling in slotsync worker

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Cc: "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fix LOCK_TIMEOUT handling in slotsync worker
Date: 2025-12-09 05:34:02
Message-ID: CAA4eK1JjO0dtFk+GH37TsSVd4pkFwmm=j5rd0UEPDnBJSuOo_Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 8, 2025 at 1:06 PM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nico Williams 2025-12-09 05:35:42 Re: [Patch] Add WHERE clause support to REFRESH MATERIALIZED VIEW
Previous Message Tom Lane 2025-12-09 05:33:20 Re: add some errhint for regexp* functions.