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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: MauMau <maumau307(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [bug fix] strerror() returns ??? in a UTF-8/C database with LC_MESSAGES=non-ASCII
Date: 2013-09-09 17:44:33
Message-ID: 22995.1378748673@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2013-09-09 17:55:51 Re: [PERFORM] encouraging index-only scans
Previous Message Stephen Frost 2013-09-09 17:31:22 Re: Custom Plan node