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

From: "MauMau" <maumau307(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Greg Stark" <stark(at)mit(dot)edu>, "Andres Freund" <andres(at)2ndquadrant(dot)com>, "PostgreSQL-development" <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-12-02 10:36:01
Message-ID: F4946C5ACBC045CFB5EAF35954C83F91@maumau
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi, Tom san,

From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> I've committed this with some editorialization (mostly, I used a case
> statement not a constant array, because that's more like the other places
> that switch on errnos in this file).
>
>> As I said, lack of %m string has been making troubleshooting difficult,
>> so I
>> wish this to be backported at least 9.2.
>
> I'm waiting to see whether the buildfarm likes this before considering
> back-patching.

I'm very sorry to respond so late. Thank you so much for committingthe
patch. I liked your code and comments.

I'll be glad if you could back-port this. Personally, in practice, 9.1 and
later will be sufficient.

Regards
MauMau

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2013-12-02 10:52:08 Re: [bug fix] strerror() returns ??? in a UTF-8/C database with LC_MESSAGES=non-ASCII
Previous Message Andres Freund 2013-12-02 10:07:25 Re: In-core regression tests for replication, cascading, archiving, PITR, etc.