mirror of https://github.com/postgres/postgres
Using DEFAULT_COLLATION_OID in the comparePartial functions was not only a lame hack, but outright wrong, because the compare functions for collation-aware types were already responding to the declared index collation. So comparePartial would have the wrong expectation about the index's sort order, possibly leading to missing matches for prefix searches.pull/1/head
parent
78e7e20afe
commit
474ff212e5
Loading…
Reference in new issue