Re: collations in shared catalogs?

>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

>> So while helping someone with an unrelated issue, I did a quick
>> query to look for collation-dependent indexes, and was rather
>> shocked to find that not only are there two such in the system
>> catalogs, both set to "default" collation, but that one of them is
>> in a _shared_ catalog (pg_shseclabel).

>> How did that happen? And how could it possibly work?

Tom> It probably doesn't, and the reason nobody has noticed is that the
Tom> security label stuff has fewer users than I have fingers (and
Tom> those people aren't using provider names that would cause anything
Tom> interesting to happen).

Or possibly not mixing locales between databases.

Tom> The most obvious fix is to change "provider" to a NAME column.

Tom> What was the other case? We might want to add a regression test
Tom> to check for collation-dependent system indexes ...

pg_seclabel (also "provider").

--
Andrew (irc:RhodiumToad)