Am 18.08.2014 15:31, schrieb holger.friedrich-fa-triva...@it.nrw.de:
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, s
Am 18.08.2014 17:50, schrieb holger.friedrich-fa-triva...@it.nrw.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
-triva...@it.nrw.de
Sent: Monday, August 18, 2014 5:51 PM
To: pgsql-general@postgresql.org
Cc: redo...@tortenboxer.de
Subject: Re: [GENERAL] 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
o so regardless.
-Original Message-
From: Redoute [mailto:redo...@tortenboxer.de]
Sent: Monday, August 18, 2014 5:00 PM
To: Friedrich-Fa-Trivadis, Holger (IT.NRW); pgsql-general@postgresql.org
Subject: Re: [GENERAL] logfile character encoding
Am 18.08.2014 15:31, schrieb holger.friedrich-fa-tri
Am 18.08.2014 15:31, schrieb holger.friedrich-fa-triva...@it.nrw.de:
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
➢ Yeah, more digging on my part seems to indicate that no matter what you
➢ do Windows is going to set the locale to some variety of a codepage.
➢ Unfortunately, I do not use Windows enough to go much further with this.
➢ Hopefully someone more Microsoft fluent can weigh in on this, as this
➢ i
On 08/17/2014 03:32 PM, Redoute wrote:
Am 17.08.2014 17:17, schrieb Tom Lane:
Me too, but I repeat the point that what you have to twiddle is the
postmaster's environment; in particular you have to set LC_CTYPE
(or maybe better LC_ALL), which cannot be set from the config file.
With "set LC_C
Am 17.08.2014 17:17, schrieb Tom Lane:
> Me too, but I repeat the point that what you have to twiddle is the
> postmaster's environment; in particular you have to set LC_CTYPE
> (or maybe better LC_ALL), which cannot be set from the config file.
With "set LC_CTYPE" do you mean to create an simple
Am 17.08.2014 16:49, schrieb Adrian Klaver:
> Here is a blog
> that seems to address your issue somewhat:
>
> http://www.g-loaded.eu/2011/02/27/locale-windows/
This seems somewhat confused. But it made me playing with initdb, which
I did not try before.
I got:
> >initdb.exe --locale=american_u
Adrian Klaver writes:
> On 08/17/2014 03:30 AM, Redoute wrote:
>> Am 16.08.2014 21:40, schrieb Tom Lane:
>>> You need to make sure the postmaster's
>>> environment selects a UTF8 locale.
>> So is this possible at all in Windows?
> I am afraid Windows locale setting is a mystery to me.
Me too, b
On 08/17/2014 03:30 AM, Redoute wrote:
Am 16.08.2014 21:40, schrieb Tom Lane:
You need to make sure the postmaster's
environment selects a UTF8 locale.
So is this possible at all in Windows?
http://msdn.microsoft.com/en-us/goglobal/bb896001.aspx
According to this table Locales support ANSI an
Am 16.08.2014 21:40, schrieb Tom Lane:
> You need to make sure the postmaster's
> environment selects a UTF8 locale.
So is this possible at all in Windows?
http://msdn.microsoft.com/en-us/goglobal/bb896001.aspx
According to this table Locales support ANSI and OEM codepages, but
there is no mentio
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 message
On 08/16/2014 12:26 PM, Redoute wrote:
Hello,
please help me with this problem: My postgreSQL logfiles generally are
encoded in UTF-8, but some entries are in Windows-1252. The server
status in pgAdmin III doesn't cope with this; it is unusable because of
continuous error popups.
log destinat
Redoute writes:
> please help me with this problem: My postgreSQL logfiles generally are
> encoded in UTF-8, but some entries are in Windows-1252. The server
> status in pgAdmin III doesn't cope with this; it is unusable because of
> continuous error popups.
> I found several discussions regardin
Hello,
please help me with this problem: My postgreSQL logfiles generally are
encoded in UTF-8, but some entries are in Windows-1252. The server
status in pgAdmin III doesn't cope with this; it is unusable because of
continuous error popups.
I found several discussions regarding this issue, e. g.
16 matches
Mail list logo
