Re: problem with glibc strerror messages translation

On 10/16/2010 08:58 PM, Robert Haas wrote:
> 2010/10/13 Sergey Burladyan<eshkinkot@gmail.com>:
>> IMHO you can receive question-marks here if lc_messages in postgresql.conf
>> do not match with locale from environment at server start, for example:
>>
>> correctly translated and displayed:
>> $ LANG=ru_RU.UTF-8 ../bin/postgres -D d -k`pwd`/s
>> 2010-10-13 05:34:39 MSD 14796 4cb50caf.39cc FATAL:  XX000: could not create shared memory segment: îÅÄÏÐÕÓÔÉÍÙÊ
ÁÒÇÕÍÅÎÔ
>>
>> incorrect, question-marks only:
>> $ LANG=C ../bin/postgres -D d -k`pwd`/s
>> 2010-10-13 05:34:54 MSD 14798 4cb50cbd.39ce FATAL:  XX000: could not create shared memory segment: ????????????
????????
>
> This seems like it might be a bug.  Can we fix it by initializing...
> something... a bit more thoroughly than we presently do?

There was a previous discussion about this re logs that mixed the
shift-JIS and UTF-8 encodings on a Japanese language machine. It came up
under "BUG #5661: The character encoding in logfile is confusing". I've
CC'd the reporter of that bug in on this discussion, as it appears to be
pertinent.

Tom didn't seem to like any of the options I raised as possible
solutions to the mixed encoding issue, and the discussion petered out
with things being left at the (IMO broken) status quo.

See:

http://www.mail-archive.com/pgsql-bugs@postgresql.org/msg28047.html
http://www.mail-archive.com/pgsql-hackers@postgresql.org/msg159818.html
http://www.mail-archive.com/pgsql-hackers@postgresql.org/msg159872.html

--
Craig Ringer