Re: BUG: Incorrect working with POSIX locale if database in UTF-8 encoding

From: "Jehan-Guillaume (ioguix) de Rorthais" <ioguix(at)free(dot)fr>
To: Олег Самойлов <splarv(at)ya(dot)ru>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG: Incorrect working with POSIX locale if database in UTF-8 encoding
Date: 2018-10-18 13:45:04
Message-ID: 20181018154504.2e87ee54@firost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 17 Oct 2018 12:29:52 +0300
Олег Самойлов <splarv(at)ya(dot)ru> wrote:

> There is not problem with systemctl, if system locale setted by localectl is
> the same as database locale. But, as I said, there is problem with pacemaker
> pgsqlms module. And I think this is incorrect behavior. Database may write in
> log messages in database locale, if this messages arises inside connection to
> this database. But common messages, such as messages on start cluster or
> errors on start cluster must written according to locale settings, and if
> locale empty (POSIX) such messages must be in english. And if messages not in
> english they must be visible as is, not as ‘???’. :) It works inside
> connection, why this does not work on start/stop?

It seems like POSIX support ASCII and some additional characters. So maybe the
character encoding used in the database is just incompatible with POSIX, ie.
POSIX does not support wide chars. As you can see, characters from ASCII table
are printed correctly.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dinko Papak 2018-10-18 13:49:52 Help with list partitioning on expression
Previous Message Adrian Klaver 2018-10-18 13:30:41 Re: convert real to numeric.