From: | Олег Самойлов <splarv(at)ya(dot)ru> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
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-17 12:22:52 |
Message-ID: | E09FEB26-BE2F-4738-A0D6-24B49563BF15@ya.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Don’t agree. Pgsqlms just run pg_ctl with POSIX locale, this is not a bug. But unreadable messages when locale charset don’t match database charset is bug of pg_ctl. When messages come from within connection all fine, why don’t do the same for messages on start/stop?
> 17 окт. 2018 г., в 15:13, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> написал(а):
>
> On 10/17/18 2:29 AM, Олег Самойлов wrote:
>> I think this is a bug, because database encoding logging must work even in this case. The main problem is with pacemaker module pgsqlms, which launch pg_ctl in empty environment and thus with broken logging.
>
> I suggest filing an issue here:
>
> https://github.com/ClusterLabs/PAF/issues
>
>
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Ravi Krishna | 2018-10-17 15:17:11 | Re: postgres server process crashes when using odbc_fdw |
Previous Message | Adrian Klaver | 2018-10-17 12:13:33 | Re: BUG: Incorrect working with POSIX locale if database in UTF-8 encoding |