Re: Question -- why is there no errhint_internal function?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Smith <smithpb2250(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Question -- why is there no errhint_internal function?
Date: 2025-02-04 00:54:19
Message-ID: 547688.1738630459@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Smith <smithpb2250(at)gmail(dot)com> writes:
> I noticed today that there is no 'errhint_internal' function partner
> for the 'errhint' function.

> Now, it might seem that hints are always intended for user output so
> of course, you'll always want them translated...

Yeah, I think that was the reasoning. If it needs a hint it must be
a user-facing error.

> but there are some
> calls to this function (like below) where the actual hint message is
> already built and translated before %s parameter substitution, so
> AFAICT translation aka gettext lookup of just a "%s" format string
> doesn't really achieve anything.

There are lots of places where we don't worry about that overhead.
I'm not excited about trying to get rid of it everywhere --- surely
these paths are not very performance-critical?

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-02-04 00:58:35 Re: Better title output for psql \dt \di etc. commands
Previous Message Greg Sabino Mullane 2025-02-04 00:47:39 Re: Better title output for psql \dt \di etc. commands