Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail
Date
Msg-id 20160216200614.GI31273@momjian.us
Whole thread Raw
In response to Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail
Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail
List 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@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                             +

pgsql-bugs by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail
Next
From: John R Pierce
Date:
Subject: Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail