Re: [PATCH] Add hints for invalid binary encoding names in encode/decode functions - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: [PATCH] Add hints for invalid binary encoding names in encode/decode functions
Date
Msg-id CAHGQGwGvFhmsc9-74Z8+vPLGFou9FVL=QR541D8Fdnr5gU1DEA@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Add hints for invalid binary encoding names in encode/decode functions  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: [PATCH] Add hints for invalid binary encoding names in encode/decode functions
List pgsql-hackers
On Wed, Nov 19, 2025 at 10:57 PM Peter Eisentraut <peter@eisentraut.org> wrote:
> My point was a different one.  It is generally preferable to separate
> translatable and untranslated things.  So, as an example from elsewhere,
> instead of
>
> errhint("Use ALTER DOMAIN instead.");
>
> it would be better to use
>
> errhint("Use % instead.", "ALTER DOMAIN");
>
> Similarly, here I would prefer something along the lines of
>
> errhint("Valid values are \"%s\", \"%s\", and \"%s\".", "foo", "bar",
> "baz");
>
> So like it was done in patch v3 looks good to me.

Thanks for the explanation! I misunderstood your point.

So I will commit v3 patch.

Regards,

--
Fujii Masao



pgsql-hackers by date:

Previous
From: Dean Rasheed
Date:
Subject: Re: ON CONFLICT DO SELECT (take 3)
Next
From: Daniel Gustafsson
Date:
Subject: Re: [PATCH] Add hints for invalid binary encoding names in encode/decode functions