Re: Wrong Results from SP-GiST with Collations
Peter Geoghegan <pg@bowt.ie>
From: Peter Geoghegan <pg@bowt.ie>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Emre Hasegeli <emre@hasegeli.com>, Teodor Sigaev <teodor@sigaev.ru>, PostgreSQL Bugs <pgsql-bugs@postgresql.org>
Date: 2018-04-16T19:58:52Z
Lists: pgsql-bugs
On Mon, Apr 16, 2018 at 12:55 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > I'm not following --- varstr_cmp has no way to know that we only > care about equality vs inequality. Yes, it might give back an > answer quickly when the strings are equal, but when they aren't, > it has to decide which is greater. In this case we don't care, > so long as the search operator is "=". That was the subtlety I was missing. I didn't understand what you meant, but thought that the fast-path might be relevant. Clearly not. -- Peter Geoghegan
Commits
-
Fix broken collation-aware searches in SP-GiST text opclass.
- b15e8f71dbf0 11.0 landed
- d90b2904c711 9.6.9 landed
- cf73a5b34a90 9.3.23 landed
- 93053aca5400 9.5.13 landed
- 608d1f97114d 9.4.18 landed
- 3397c67272e2 10.4 landed
-
Add prefix operator for TEXT type.
- 710d90da1fd8 11.0 cited