| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, Jan Lentfer <jan(dot)lentfer(at)web(dot)de> |
| Cc: | Tatsuo Ishii <ishii(at)postgresql(dot)org>, <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-16 19:36:24 |
| Message-ID: | 56C37A38.6060007@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2/16/16 10:38 AM, Bruce Momjian wrote:
> 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.
Could we force the global catalogs to always be accessed via UTF8, at
least for modification? I suspect that would mean changing encodings on
the fly in the appropriate command functions (such as what's listed in
src/include/commands/user.h).
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2016-02-16 20:06:14 | Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail |
| Previous Message | Bruce Momjian | 2016-02-16 16:38:33 | Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail |