Re: Invalid primary_slot_name triggers warnings in all processes on reload - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Invalid primary_slot_name triggers warnings in all processes on reload
Date
Msg-id CAA4eK1J3aJbRd+JU3mKoVhs99oK5gbEGTjegbCORfu4p1Lv_gw@mail.gmail.com
Whole thread Raw
In response to RE: Invalid primary_slot_name triggers warnings in all processes on reload  ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>)
List 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 by date:

Previous
From: shveta malik
Date:
Subject: Re: Logical Replication of sequences
Next
From: "iosif"
Date:
Subject: There is a redundant check in check_outerjoin_delay() in version 15.14 and below