Re: [bug fix] strerror() returns ??? in a UTF-8/C database with LC_MESSAGES=non-ASCII

On 2013-09-06 10:37:16 -0400, Tom Lane wrote:
> "MauMau" <maumau307@gmail.com> writes:
> > I've been suffering from PostgreSQL's problems related to character encoding 
> > for some time.  I really wish to solve those problems, because they make 
> > troubleshooting difficult.  I'm going to propose fixes for them, and I would 
> > appreciate if you could help release the official patches as soon as 
> > possible.
> 
> I don't find either of these patches to be a particularly good idea.
> There is certainly no way we'd risk back-patching something with as
> many potential side-effects as fooling with libc's textdomain.

I have no clue about the gettext stuff but I am in favor of including
the raw errno in strerror() messages (no backpatching tho). When doing
support it's a PITA to get translated strings for those. I can lookup
postgres' own translated messages in the source easy enough, but that
doesn't work all that well for OS supplied messages.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services