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 CAA4eK1+GeaAnbpC=4KdMvW8n5ASrpOeA1b1nhci8Zu4a9hZAVA@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
List pgsql-hackers
On Tue, Dec 9, 2025 at 11:23 AM Chao Li <li.evan.chao@gmail.com> wrote:
>
>
> Yeah, I just searched and see similar messages:
>
> ```
> logical replication parallel apply worker for subscription \"%s\" will stop because the subscription owner's
superuserprivileges have been revoked 
>
> logical replication worker for subscription \"%s\" will restart because the subscription owner's superuser privileges
havebeen revoked 
> ```
>
> I think the new phrase is better. Maybe “is triggered” could be “has been triggered”?
>

My AI tool says:

Both options are grammatically correct, but the nuance differs:
"will stop because promotion is triggered"
This uses the present tense ("is triggered"), which suggests the
promotion event is happening right now, concurrently with the stopping
action.
"will stop because promotion has been triggered"
This uses the present perfect tense ("has been triggered"), which
implies the promotion event already occurred and is the reason for the
upcoming stop.

In this case, because ShutDownSlotSync() will wait for the slotsync
worker to exit, so the first one ("will stop because promotion is
triggered") fits better.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: "Zhijie Hou (Fujitsu)"
Date:
Subject: RE: Fix LOCK_TIMEOUT handling in slotsync worker
Next
From: Chao Li
Date:
Subject: Re: Fix LOCK_TIMEOUT handling in slotsync worker