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

On 2/16/16 2:10 PM, John R Pierce wrote:
>>> >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 ?

You could probably make an argument for SQL_ASCII.

The part about all of this that concerns me is what happens when people
query global catalogs directly... I'm not sure if we have the ability to
force specific conversions when that happens.
--
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