From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Redoute <redoute(at)tortenboxer(dot)de>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: logfile character encoding |
Date: | 2014-08-16 21:19:35 |
Message-ID: | 53EFCAE7.6000105@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 08/16/2014 12:26 PM, Redoute wrote:
> Hello,
>
>
> log destination is configured as stderr, with logging collector on
> (default setup). So it may be one issue that stderr is written in 1252
> (not sure about that), but then why are most logfile entries encoded in
> UTF-8? Is only a part of all messages routed via stderr?
>
> Another idea is that the 1252 encodings may be related to pgAdmin III? I
> send almost all SQL via its query window.
>
> Windows 8.1
> PostgreSQL 9.3.5 64 bit
> pgAdmin 1.18.1
> database encoding UTF8
> all on the same PC, no multiple servers or database encodings involved
Aaah, missed Toms post that explained the discrepancy better. In other
words database is operating in one encoding, the postmaster in another.
That would explain my previous observation.
> Thanks, Redoute
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | BladeOfLight16 | 2014-08-16 22:27:14 | Re: Support functions for GiST index on citext |
Previous Message | Adrian Klaver | 2014-08-16 21:09:18 | Re: logfile character encoding |