From: | Jan Lentfer <jan(dot)lentfer(at)web(dot)de> |
---|---|
To: | pgadmin-support(at)postgresql(dot)org |
Subject: | pgadmin3 using wrong encoding for "COMMENT ON DATABASE .." (at least) |
Date: | 2016-01-27 08:03:51 |
Message-ID: | ea43df7d703ad4c8e84671ead676152a@neslonek.homeunix.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
I would like to point you to this thread on pgsql-bugs:
http://www.postgresql.org/message-id/666abab3fe03561c77dbfc661b023985@neslonek.homeunix.org
It seems that, when using a SQL_ASCII encoded database as the initial
connection DB for pgadmin3 and then using the "properties" windows to
set the comment on an UTF-8 encoded database, pgadmin will actually
write the comment in SQL_ASCII encoding on to the UTF-8 database. When
using special characters like the german umlauts (äöü) this causes
pg_restore -C to throw errors because of invalid encoding and it leads
to pg_upgrade to fail completely.
I have tested this with pgadmin3 1.20.0 on Windows 8.1 with Postgres
9.4.5 both on Solaris 11 and Debian Jessie. But we have been bitten by
this problem approx 2-3 ago also.
Best regards
Jan
From | Date | Subject | |
---|---|---|---|
Next Message | basil.bourque.lists | 2016-01-28 04:17:21 | Crash when changing font in Preferences > Query tool |
Previous Message | Dave Page | 2016-01-26 11:39:10 | Re: pgadmin crashes constantly on OSX 10.11.1 |