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

On Wed, Jan 27, 2016 at 08:44:27AM +0100, Jan Lentfer wrote:
> 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.

I see no one else commented on this.  We have trouble keeping the global
system catalogs consistent when databases in the same cluster use
different encodings.  I am not sure how we could improve this.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription                             +