Request a Demo
Home   >   mailing lists

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

From Fujii Masao
Subject Re: Invalid primary_slot_name triggers warnings in all processes on reload
Date
Msg-id CAHGQGwHJxhaQQ7bf_wPBYBTJO+X+rK_-znsgay_kYm2ncJYAGQ@mail.gmail.com
Whole thread Raw
In response to Re: Invalid primary_slot_name triggers warnings in all processes on reload  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
Tree view 
On Wed, Oct 22, 2025 at 12:52 PM Fujii Masao <masao.fujii@gmail.com> wrote:
> So let's push the current patch, including only the cosmetic indentation
> changes suggested by Hayato-san.

I've pushed the patch. Thanks!

Attached is the rebased version of the patch I shared earlier, which adds
GUC_check_errmsg_internal(), GUC_check_errdetail_internal(),
and GUC_check_errhint_internal(). These functions work like
their counterparts (e.g., GUC_check_errmsg()) but skip translation.
The patch also updates the check hook for primary_slot_name to use
these new functions when handling already-translated error messages.
If we apply this patch, I'm thinking to push it to master only.

Regards,

--
Fujii Masao
Attachment

pgsql-hackers by date:

Previous
From: Akshay Joshi
Date:
Subject: Re: [PATCH] Add pg_get_policy_ddl() function to reconstruct CREATE POLICY statement
Next
From: Andres Freund
Date:
Subject: Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?