Re: logfile character encoding

From: Redoute <redoute(at)tortenboxer(dot)de>
To: Holger(dot)Friedrich-Fa-Trivadis(at)it(dot)nrw(dot)de, pgsql-general(at)postgresql(dot)org
Subject: Re: logfile character encoding
Date: 2014-08-18 16:20:12
Message-ID: 53F227BC.6040108@tortenboxer.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Am 18.08.2014 17:50, schrieb Holger(dot)Friedrich-Fa-Trivadis(at)it(dot)nrw(dot)de:

> initdb.exe --locale=German_Germany --encoding=UTF-8
>
> which the link implies seems to have worked for its author?

I have tried a bunch of similar program calls and posted them last night
as answer to Adrian. --encoding=UTF-8 sets the default database
encoding, but this leaves the "Postmaster" itself at 1252. This is
indicated by initdb's output, and your proposal gives exactly the setup
that the installer does by default and which causes mixed logfile encodings.

As all my tests show, the "Postmaster" is bound to a valid Locale, and
Unicode encodings are never part of valid Locales in Windows, so a
Windows "Postmaster" will never write UTF-8 output.

Please note that the example in the block uses english language, so the
author probably will not have noticed 1252 encodings. The english
messages also don't have fancy (if not silly) quotation marks like the
german ones.

Thanks,
Redoute

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Granthana 2014-08-18 16:49:07 Re: .pgpass being ignored
Previous Message Holger.Friedrich-Fa-Trivadis 2014-08-18 15:54:49 FW: logfile character encoding