| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
| Cc: | Jan Lentfer <jan(dot)lentfer(at)web(dot)de>, 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 20:06:14 |
| Message-ID: | 20160216200614.GI31273@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Feb 16, 2016 at 01:36:24PM -0600, Jim Nasby wrote:
> 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).
I don't remember us favoring UTF8 in this way in the past.
--
Bruce Momjian <bruce(at)momjian(dot)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 +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2016-02-16 20:10:08 | Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail |
| Previous Message | Jim Nasby | 2016-02-16 19:36:24 | Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail |