Re: Invalid primary_slot_name triggers warnings in all processes on reload

Поиск
Список
Период
Сортировка
От Amit Kapila
Тема Re: Invalid primary_slot_name triggers warnings in all processes on reload
Дата
Msg-id CAA4eK1J3aJbRd+JU3mKoVhs99oK5gbEGTjegbCORfu4p1Lv_gw@mail.gmail.com
обсуждение исходный текст
Ответ на RE: Invalid primary_slot_name triggers warnings in all processes on reload  ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>)
Ответы Re: Invalid primary_slot_name triggers warnings in all processes on reload
Список pgsql-hackers
On Tue, Oct 21, 2025 at 2:36 PM Hayato Kuroda (Fujitsu)
<kuroda.hayato@fujitsu.com> wrote:
>
> > Just to confirm - you'd prefer backpatching errhint_internal() to v17 and
> > earlier branches, and then updating the patch to use it to avoid double
> > translation, right?
>
> Exactly, but I want to ask other Seniors as well.
>

I don't think it is important enough to backpatch errhint_internal to
v17 and earlier branches. We can let double translation happen with
the use of errhint or we can even consider this as a HEAD only
improvement because this is not a blocking issue even when it happens.

--
With Regards,
Amit Kapila.



В списке pgsql-hackers по дате отправления: