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

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: bruce(at)momjian(dot)us
Cc: jan(dot)lentfer(at)web(dot)de, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail
Date: 2016-02-17 00:25:51
Message-ID: 20160217.092551.1123903508583964153.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> 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.

Long time ago I proposed an idea to solve this kind of problems:

http://www.postgresql.org/message-id/20131112.155752.666523035722474275.t-ishii@sraoss.co.jp

The implementation details are not necessarily the best but still I
believe what we need is "round trip encoding conversion safe"
universal encoding for internal use.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jim Nasby 2016-02-17 01:23:38 Re: BUG #13960: plpython fails with certain function names
Previous Message Bruce Momjian 2016-02-17 00:01:47 Re: Documentation Error - Update YUM repository page to reflect 9.5 support