Horton

Re: Invalid primary_slot_name triggers warnings in all processes on reload

Amit Kapila <amit.kapila16@gmail.com>

View thread View on postgr.es
From: Amit Kapila <amit.kapila16@gmail.com>
To: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
Cc: Fujii Masao <masao.fujii@gmail.com>, Álvaro Herrera <alvherre@kurilemu.de>, Chao Li <li.evan.chao@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-10-21T10:27:46Z
Lists: 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.

Commits

  1. Make invalid primary_slot_name follow standard GUC error reporting.