On Wed, Jul 24, 2024 at 3:12 PM Jeff Davis <pg...@j-davis.com> wrote: > In any case, you are correct that Unicode updates could put some > constraints at risk, including unique indexes, CHECK, and partition > constraints. But someone has to actually use one of the affected > functions somewhere, and that's the main distinction that I'm trying to > draw. > > The reason why collation is qualitatively a much bigger problem is > because there's no obvious indication that you are doing anything > related to collation at all. A very plain "CREATE TABLE x(t text > PRIMARY KEY)" is at risk.
Well, I don't know. I agree that collation is a much bigger problem, but not for that reason. I think a user who is familiar with the problems in this area will see the danger either way, and one who isn't, won't. For me, the only real difference is that a unique index on a text column is a lot more common than one that involves UPPER. -- Robert Haas EDB: http://www.enterprisedb.com
