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

From: John R Pierce <pierce(at)hogranch(dot)com>
To: 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:10:08
Message-ID: 56C38220.9060900@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jim Nasby 2016-02-16 20:12:41 Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail
Previous Message Bruce Momjian 2016-02-16 20:06:14 Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail