| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, kksrcv001(at)gmail(dot)com, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: Add missing error codes to PANIC/FATAL error reports in xlog.c and relcache.c |
| Date: | 2024-02-23 12:33:07 |
| Message-ID: | 2F60920E-74C4-4FB3-93D5-670890A53B99@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 23 Feb 2024, at 13:09, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> wrote:
> Does errmsg_internal() need to be used all the time when turning elogs
> into ereports? errmsg_internal()'s comment says that "This should be
> used for "can't happen" cases that are probably not worth spending
> translation effort on.". Is it enough to check if the error message
> has a translation, and then decide the use of errmsg_internal() or
> errmsg()?
If it's an elog then it won't have a translation as none are included in the
translation set. If the errmsg is generic enough to be translated anyways via
another (un)related ereport call then we of course use that, but ideally not
create new ones.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2024-02-23 12:35:38 | Re: table inheritance versus column compression and storage settings |
| Previous Message | Nazir Bilal Yavuz | 2024-02-23 12:09:26 | Re: Add missing error codes to PANIC/FATAL error reports in xlog.c and relcache.c |