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

From Tom Lane
Subject Re: [bug fix] strerror() returns ??? in a UTF-8/C database with LC_MESSAGES=non-ASCII
Date
Msg-id 22995.1378748673@sss.pgh.pa.us
Whole thread Raw
In response to Re: [bug fix] strerror() returns ??? in a UTF-8/C database with LC_MESSAGES=non-ASCII  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> On 9/9/13 10:25 AM, Tom Lane wrote:
>> Meh.  Seems that would only prevent one specific instance of the general
>> problem that strerror can fail to translate its result.  Other locale
>> combinations might create the same kind of failure.

> True.  There isn't much we can do, really.  If your LC_MESSAGES and
> LC_CTYPE don't get along, you get what you asked for.  This isn't
> specific to PostgreSQL:

So should we just say this is pilot error?  It may be, but if we can work
around it with a reasonably small amount of effort/risk, I think it's
appropriate to do that.  The proposal to reject a strerror result that
starts with '?' sounds plausible to me.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Custom Plan node
Next
From: Bruce Momjian
Date:
Subject: Re: [PERFORM] encouraging index-only scans