| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general pgsql-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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Law | 2012-07-19 08:21:45 | Re: main log encoding problem |
| Previous Message | Tatsuo Ishii | 2012-07-19 07:49:51 | Re: main log encoding problem |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Law | 2012-07-19 08:21:45 | Re: main log encoding problem |
| Previous Message | Daniel McGreal | 2012-07-19 08:04:58 | GENERATED columns |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Law | 2012-07-19 08:21:45 | Re: main log encoding problem |
| Previous Message | Tatsuo Ishii | 2012-07-19 07:49:51 | Re: main log encoding problem |