I wrote: > * You're not bothering to insert any inputcollid into the generated > comparison operator nodes. I'm not sure why that fails to fall over > for text comparisons (if indeed it does fail ...) but it's wrong. > Use the range type's collation there.
Oh ... looking at this again, I realize that there's an additional validity check missing: if the range type's collation doesn't match the index column's collation, we can't do this optimization at all. That check probably belongs in match_special_index_operator. regards, tom lane -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers