Re: Invalid primary_slot_name triggers warnings in all processes on reload

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Invalid primary_slot_name triggers warnings in all processes on reload
Date: 2025-10-21 10:27:46
Message-ID: CAA4eK1J3aJbRd+JU3mKoVhs99oK5gbEGTjegbCORfu4p1Lv_gw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 21, 2025 at 2:36 PM Hayato Kuroda (Fujitsu)
<kuroda(dot)hayato(at)fujitsu(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message iosif 2025-10-21 10:58:57 There is a redundant check in check_outerjoin_delay() in version 15.14 and below
Previous Message shveta malik 2025-10-21 09:37:13 Re: Logical Replication of sequences