Re: collations in shared catalogs? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: collations in shared catalogs?
Date
Msg-id 818.1424897995@sss.pgh.pa.us
Whole thread Raw
In response to Re: collations in shared catalogs?  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: collations in shared catalogs?  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> On 2015-02-25 12:08:32 -0500, Tom Lane wrote:
>> The most obvious fix is to change "provider" to a NAME column.

> Yea. I'm not sure why that wasn't done initially. I can't really see the
> length be an issue. How about we add an error check enforcing ascii,
> that'll work in the back branches?

Nope, that won't help much at all.  C vs en_US for instance is different
sort orders even with all-ASCII data.

Basically you're screwed if you've got different collations in different
databases and you put anything into pg_shseclabel ...
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: a fast bloat measurement tool (was Re: Measuring relation free space)
Next
From: Andres Freund
Date:
Subject: Re: collations in shared catalogs?