From: | Redoute <redoute(at)tortenboxer(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: logfile character encoding |
Date: | 2014-08-17 10:30:52 |
Message-ID: | 53F0845C.8090802@tortenboxer.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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?)
Thank you,
Redoute
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2014-08-17 14:49:58 | Re: logfile character encoding |
Previous Message | Chris Hanks | 2014-08-16 23:02:50 | Re: Support functions for GiST index on citext |