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

From Greg Stark
Subject Re: [bug fix] strerror() returns ??? in a UTF-8/C database with LC_MESSAGES=non-ASCII
Date
Msg-id CAM-w4HOAeSdR+MpFu0M4q3htnaBjhU5pxqpMNG1QsEmx3incMA@mail.gmail.com
Whole thread Raw
In response to Re: [bug fix] strerror() returns ??? in a UTF-8/C database with LC_MESSAGES=non-ASCII  ("MauMau" <maumau307@gmail.com>)
Responses Re: [bug fix] strerror() returns ??? in a UTF-8/C database with LC_MESSAGES=non-ASCII
List pgsql-hackers
On Mon, Sep 9, 2013 at 11:27 PM, MauMau <maumau307@gmail.com> wrote:
> 1. Recreate the database with LC_CTYPE = ja_JP.UTF-8.  This changes various
> behaviors such as ORDER BY, index scan, and the performance of LIKE clause.
> This is almost impossible.


Wait, why does the ctype of the database affect the ctype of the
messages? Shouldn't these be two separate things? One describes the
character set being used to store data in the database and the other
the character set the log file and clients are in.

That said, we do interpolate a lot of database strings into messages.

-- 
greg



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Protocol forced to V2 in low-memory conditions?
Next
From: Greg Stark
Date:
Subject: Re: Custom Plan node