| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Álvaro Herrera <alvherre(at)kurilemu(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: NLS: use gettext() to translate system error messages |
| Date: | 2025-12-26 19:33:21 |
| Message-ID: | 3f987bda543f2c08301b404be31a2a289911301b.camel@j-davis.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2025-12-23 at 15:21 -0500, Tom Lane wrote:
> Surely RHEL8 does not pre-date glibc's ability to translate messages.
> I suspect I have some system-wide setting for this, or maybe a
> missing package on that machine?
Probably a missing language package.
> But anyway, I think this reinforces
> my point that we should (and do) act similarly to other programs.
It depends on the perspective. For a system administrator, what you say
makes sense. But from a Postgres user who is expecting consistent
translation, it can be a bit mysterious. And from an engineering
standpoint, translation through strerror() is not tested and -- as far
as I can tell -- only works on glibc.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Jacobson | 2025-12-26 20:12:40 | Re: Optimize LISTEN/NOTIFY |
| Previous Message | Jeff Davis | 2025-12-26 19:32:30 | Re: NLS: use gettext() to translate system error messages |