On Wed, Jul 24, 2024 at 3:43 PM Jeremy Schneider <schnei...@ardentperf.com> wrote: > But non-unique indexes for case insensitive searches will be more common. > Historically this is the most common way people did case insensitive on > oracle. > > Changing ctype would mean these queries can return wrong results
Yeah. I mentioned earlier that I very recently saw a customer query with UPPER() in the join condition. If someone is doing foo JOIN bar ON upper(foo.x) = upper(bar.x), it is not unlikely that one or both of those expressions are indexed. Not guaranteed, of course, but very plausible. -- Robert Haas EDB: http://www.enterprisedb.com
