Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail

From: Jan Lentfer <jan(dot)lentfer(at)web(dot)de>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail
Date: 2016-01-27 07:44:27
Message-ID: a449263f8e2ac8dc5c4454fac2b24b05@neslonek.homeunix.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Am 2016-01-27 01:45, schrieb Tatsuo Ishii:
> I am not familiar with pgadmin3 but it seems a bug with pgadmin3 or
> misuse of it to me. Probably when this:
>
>> ---> use pgadmin3 on Windows to set comment on database coment_test
>> with
>> ---> string "für", while being connected to postgres (SQL_ASCII
>> encoded)
>
> was executed, the client encoding is not properly set to UTF-8 for
> some reasons.

I think you are actually right. It seems this only happens if you
initially connect to a SQL_ASCII databse with pgadmin3 and then set a
comment containing special characters on a UTF-8 database. I could now
also reproduce this behaviour on a Linux host with Postgre 9.4.5.
And I can also confirm that this does not happen using psql.

I will forward this issue to the pgadmin mailing list.

Thanks and best regards

Jan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dmitriy Sarafannikov 2016-01-27 10:24:35 Segfault in MemoryContextAlloc
Previous Message Dmitriy Sarafannikov 2016-01-27 07:06:40 Re: [BUGS] Postgres backend segfault