Re: locale problem of bgworker: logical replication launcher and worker process

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Ioseph Kim <pgsql-kr(at)postgresql(dot)kr>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: locale problem of bgworker: logical replication launcher and worker process
Date: 2017-08-23 13:40:59
Message-ID: 8fb1a4fb-a4cf-a71e-2cca-20e19329c8b9@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 8/22/17 01:19, Ioseph Kim wrote:
> 2017-08-22 14:06:21.697 KST [306] 로그:  logical replication apply
> worker for subscription "replica_a" has started
> 2017-08-22 14:06:21.698 KST [306] 오류:  발행 서버에 연결 할 수 없음:
> ??? ??? ? ??: ??? ???
>         "localhost" (::1) ???? ??? ?? ???,
>         5432 ??? TCP/IP ??? ???? ??????.
>     ??? ??? ? ??: ??? ???
>         "localhost" (127.0.0.1) ???? ??? ?? ???,
>         5432 ??? TCP/IP ??? ???? ??????.
> -----
>
> main postmaster messages are printed  in korean well,
> but bgworker process message is not.
>
> This problem seems to have occurred because the server locale
> environment and the client's that are different.

I have tried it locally with a ko_KR locale, and it seems to work
correctly for me. Still, I can imagine there are all kinds of ways this
could go wrong in particular configurations. Could you construct a
reproducible test setup, including specific initdb and locale settings,
operating system, etc.?

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-08-23 13:45:38 Re: POC: Sharing record typmods between backends
Previous Message Robert Haas 2017-08-23 13:36:40 Re: obsolete code in pg_upgrade