On 2015-02-25 15:59:55 -0500, Tom Lane wrote: > Andres Freund <and...@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.
Ick, yes. The restriction to a charset that's encodable in all server encodings should be there additionally, but it's not sufficient :( > Basically you're screwed if you've got different collations in different > databases and you put anything into pg_shseclabel ... Hrmpf. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers