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

From John R Pierce
Subject Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail
Date
Msg-id 56C38220.9060900@hogranch.com
Whole thread Raw
In response to Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-bugs
On 2/16/2016 12:06 PM, Bruce Momjian wrote:
> 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.

what encoding SHOULD the global catalogs be in when the databases are in
different encodings?   I'm not sure there's any answer better than utf8 ?

--
john r pierce, recycling bits in santa cruz

pgsql-bugs by date:

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