Re: problem with glibc strerror messages translation (was: Could not open file pg_xlog/000000010....)

2010/10/13 Sergey Burladyan <eshkinkot@gmail.com>:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
>
>> Victor <only-victor@mail.ru> writes:
>> > Oct 12 17:53:25 localhost postgres[26997]: [1753-1] PANIC: =9Acould not
>> > open file "pg_xlog/000000010000000000000007" (log file 0, segment
>> > 7): ???????????? ????????
>>
>> Hm, where's the rest of that error message? =9AYou should certainly not
>> have gotten just question-marks there.
>
> 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=3Dru_RU.UTF-8 ../bin/postgres -D d -k`pwd`/s
> 2010-10-13 05:34:39 MSD 14796 4cb50caf.39cc FATAL: =9AXX000: could not cr=
eate shared memory segment: =EE=C5=C4=CF=D0=D5=D3=D4=C9=CD=D9=CA =C1=D2=C7=
=D5=CD=C5=CE=D4
>
> incorrect, question-marks only:
> $ LANG=3DC ../bin/postgres -D d -k`pwd`/s
> 2010-10-13 05:34:54 MSD 14798 4cb50cbd.39ce FATAL: =9AXX000: could not cr=
eate 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?

--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company