Re: Problem with pgAdmin and Server Status encode

Поиск
Список
Период
Сортировка
От Jan-Peter Seifert
Тема Re: Problem with pgAdmin and Server Status encode
Дата
Msg-id 20130304134320.138870@gmx.net
обсуждение исходный текст
Ответ на Re: Problem with pgAdmin and Server Status encode  (Guillaume Lelarge <guillaume@lelarge.info>)
Список pgadmin-support
Hello,

-------- Original-Nachricht --------
> Datum: Sat, 23 Feb 2013 15:56:50 +0100
> Von: Guillaume Lelarge <guillaume@lelarge.info>
> An: "Manuel Fdez (JVR)" <manuel.fernandez@joyeriavirgendelrocio.com>
> CC: pgadmin-support@postgresql.org
> Betreff: Re: [pgadmin-support] Problem with pgAdmin and Server Status encode

> Well, I don't know spanish but I can guess what this message says. You
> have multiple encodings on your logs, and pgadmin doesn't like that at
> all. Unfortunately, there's not much you can do. PostgreSQL only puts
> UTF8 strings in it, but if it has to output SQL queries (because you
> asked it to do so or because there are errors on these queries), they
> may contain non-UTF8 characters.

I suspect that the problem is on the server's side.
On Windows ( Windows 7 Enterprise 64-Bit ) the default German 'locale' for UTF8 set by the 'One click installer' is
"German_Germany.1252".

So instead of 'autovacuum launcher shutting down' 'Autovacuum-Launcher fährt herunter' is being logged. The problem is
thatthe ä (ae) is not encoded in UTF8 ( just one byte ). Maybe the reason is that the encoding of code page 1252 is in
factjust a one byte encoding and no conversion is being done?
 

I checked this on Ubuntu and although the locale is "de_DE.utf8" everywhere, the messages in the logs were all in
English...
 
So I use "lc_messages = 'C'" as recommended elsewhere on the list.

With best regards,

Peter





В списке pgadmin-support по дате отправления:

Предыдущее
От: Michael Shapiro
Дата:
Сообщение: object browser collapses
Следующее
От: Justin Yan
Дата:
Сообщение: pgAdmin and AWS Redshift Connection problems