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

Поиск
Список
Период
Сортировка
От Greg Stark
Тема Re: [bug fix] strerror() returns ??? in a UTF-8/C database with LC_MESSAGES=non-ASCII
Дата
Msg-id CAM-w4HOAeSdR+MpFu0M4q3htnaBjhU5pxqpMNG1QsEmx3incMA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [bug fix] strerror() returns ??? in a UTF-8/C database with LC_MESSAGES=non-ASCII  ("MauMau" <maumau307@gmail.com>)
Ответы Re: [bug fix] strerror() returns ??? in a UTF-8/C database with LC_MESSAGES=non-ASCII  ("MauMau" <maumau307@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: Protocol forced to V2 in low-memory conditions?
Следующее
От: Greg Stark
Дата:
Сообщение: Re: Custom Plan node