Search Postgresql Archives

FW: logfile character encoding

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sorry for misquoting, the command line that reportedly worked had --encoding=UTF8 not --encoding=UTF-8.  I apologize for not paying more attention.


-----Original Message-----
From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-owner@xxxxxxxxxxxxxx] On Behalf Of Holger.Friedrich-Fa-Trivadis@xxxxxxxxx
Sent: Monday, August 18, 2014 5:51 PM
To: pgsql-general@xxxxxxxxxxxxxx
Cc: redoute@xxxxxxxxxxxxxx
Subject: Re:  logfile character encoding

What about taking a cue from the link provided by Adrian, http://www.g-loaded.eu/2011/02/27/locale-windows/, and initdb a new empty database cluster not like

initdb.exe --locale=German_Germany.UTF-8

which you say does not work, but rather like

initdb.exe --locale=German_Germany  --encoding=UTF-8

which the link implies seems to have worked for its author?  You could then check the postgresql.conf file for the new database cluster and see what lc_messages has been set to, maybe that will work for you.

Sorry I haven't tried out this idea myself -- around here we have PostgreSQL installed either on Linux servers or on virtual Linux machines, so I use Windows basically to read my e-mail (and, of course, to run VirtualBox, PuTTY and WinSCP) -- PostgreSQL isn't supposed to be installed on the Windows box, and anyway I don't have an admin password to do so regardless.


-----Original Message-----
From: Redoute [mailto:redoute@xxxxxxxxxxxxxx]
Sent: Monday, August 18, 2014 5:00 PM
To: Friedrich-Fa-Trivadis, Holger (IT.NRW); pgsql-general@xxxxxxxxxxxxxx
Subject: Re:  logfile character encoding

Am 18.08.2014 15:31, schrieb Holger.Friedrich-Fa-Trivadis@xxxxxxxxx:

> Wikipedia says that UTF-8 is code page 65001, in Microsoft notation 
> (see http://en.wikipedia.org/wiki/Code_page). Does this help in any 
> way (i.e. does German_Germany.65001 work for you)?

No, I tried that value yesterday, see my answer to Adrian.

It seems Unicode encodings are just not target of Windows Locales. Which in my opinion is reasonable: Why should it be a localization issue, how a program writes Unicode to a file? When a localized Windows suggests two different 8bit-charsets for usage (ANSI and OEM), this doesn't hinder a program to write Unicode. Why can't PostgreSQLs "Postmaster" do it?

Thanks,
Redoute

--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux