Re: Fix LOCK_TIMEOUT handling in slotsync worker
| От | Amit Kapila |
|---|---|
| Тема | Re: Fix LOCK_TIMEOUT handling in slotsync worker |
| Дата | |
| Msg-id | CAA4eK1JjO0dtFk+GH37TsSVd4pkFwmm=j5rd0UEPDnBJSuOo_Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Fix LOCK_TIMEOUT handling in slotsync worker (Chao Li <li.evan.chao@gmail.com>) |
| Ответы |
Re: Fix LOCK_TIMEOUT handling in slotsync worker
RE: Fix LOCK_TIMEOUT handling in slotsync worker |
| Список | 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 по дате отправления: