| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: Invalid encoding of process output |
| Date: | 2017-11-09 13:52:25 |
| Message-ID: | CA+OCxozk8Q_Ywf4aG+4+gJ1s7XWUwjyHu1B1+z_rCKXhZ1d=cw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Thanks, patch applied.
On Thu, Nov 9, 2017 at 2:10 AM, Alexander Lakhin <exclusion(at)gmail(dot)com>
wrote:
> Hello,
> While trying to perform backup with Russian-speaking PostgreSQL 10 (on
> Linux) I get the following unreadable messages:
>
>
>
> This bug is caused by the ansi encoding chosen when reading the process
> log file.
> Please look at the proposed fix. (It corresponds to all the other
> sys.getdefaultencoding() calls in the code.)
>
> Best regards,
> ------
> Alexander Lakhin
> Postgres Professional: http://www.postgrespro.com
> The Russian Postgres Company
>
>
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgAdmin 4 Jenkins | 2017-11-09 14:03:57 | Build failed in Jenkins: pgadmin4-master-python34 #367 |
| Previous Message | Dave Page | 2017-11-09 13:52:00 | pgAdmin 4 commit: Fix utility output capture encoding. Fixes #2854 |