Re: logfile character encoding
От | Adrian Klaver |
---|---|
Тема | Re: logfile character encoding |
Дата | |
Msg-id | 53F0C116.3040104@aklaver.com обсуждение исходный текст |
Ответ на | Re: logfile character encoding (Redoute <redoute@tortenboxer.de>) |
Ответы |
Re: logfile character encoding
Re: logfile character encoding |
Список | pgsql-general |
On 08/17/2014 03:30 AM, Redoute wrote: > Am 16.08.2014 21:40, schrieb Tom Lane: > >> You need to make sure the postmaster's >> environment selects a UTF8 locale. > > So is this possible at all in Windows? > http://msdn.microsoft.com/en-us/goglobal/bb896001.aspx > According to this table Locales support ANSI and OEM codepages, but > there is no mention of Unicode encodings. Don't know what ANSI codepage > "0" or OEM codepage "1" means, anyway this is not given for german or > english language. > > I tried to change the lc_messages configuration variable in > postgresql.conf. Setting has been > >> # These settings are initialized by initdb, but they can be changed. >> lc_messages = 'German_Germany.1252' # locale for system error message > > I tried to change it to German_Germany.UTF-8, which caused a fallback to > english messages. May be because the value is invalid at all, or may be > because there are no translations for this locale. (BTW having messages > in english seems to be a usable work-around, since these messages are > ASCII only. It is also possible to manually set lc_messages back to > 'German_Germany.1252' per session, so that the logfile contains english > messages from the "postmaster" and UTF-8 encoded german messages from > the sessions. But would this be a solution for default Windows > installations?) I am afraid Windows locale setting is a mystery to me. Here is a blog that seems to address your issue somewhat: http://www.g-loaded.eu/2011/02/27/locale-windows/ Hope it helps. > > Thank you, > Redoute > > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: