Skip site navigation (1) Skip section navigation (2)

Re: main log encoding problem

From: Alexander Law <exclusion(at)gmail(dot)com>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: ringerc(at)ringerc(dot)id(dot)au, pgsql-general(at)postgresql(dot)org, yi(dot)codeplayer(at)gmail(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: main log encoding problem
Date: 2012-07-19 08:12:17
Message-ID: 5007C161.7070100@gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-generalpgsql-hackers
>> The initial issue was that log file contains messages in different
>> encodings. So transcoding is performed already, but it's not
> This is not true. Transcoding happens only when PostgreSQL is built
> with --enable-nls option (default is no nls).
I'll restate the initial issue as I see it.
I have Windows and I'm installing PostgreSQL for Windows (latest 
version, downloaded from enterprise.db). Then I create a database with 
default settings (with UTF-8 encoding), do something wrong in my DB and 
get such a log file with the two different encodings (UTF-8 and 
Windows-1251 (ANSI)) and with localized postgres messages.


In response to

pgsql-hackers by date

Next:From: Alexander LawDate: 2012-07-19 08:21:45
Subject: Re: main log encoding problem
Previous:From: Tatsuo IshiiDate: 2012-07-19 07:49:51
Subject: Re: main log encoding problem

pgsql-bugs by date

Next:From: Alexander LawDate: 2012-07-19 08:21:45
Subject: Re: main log encoding problem
Previous:From: Tatsuo IshiiDate: 2012-07-19 07:49:51
Subject: Re: main log encoding problem

pgsql-general by date

Next:From: Alexander LawDate: 2012-07-19 08:21:45
Subject: Re: main log encoding problem
Previous:From: Daniel McGrealDate: 2012-07-19 08:04:58
Subject: GENERATED columns

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group