Postgres Pro
Downloads
Home   >   mailing lists

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

From Jim Nasby
Subject Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail
Date
Msg-id 56C37A38.6060007@BlueTreble.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
List pgsql-bugs
Tree view 
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

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: Bruce Momjian
Date:
Subject: Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail