Re: Supporting = operator in gin/gist_trgm_ops
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Julien Rouhaud <rjuju123@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-10-25T21:03:21Z
Lists: pgsql-hackers
Julien Rouhaud <rjuju123@gmail.com> writes: > A french user recently complained that with an index created using > gin_trgm_ops (or gist_trgm_ops), you can use the index with a clause > like > col LIKE 'something' > but not > col = 'something' Huh, I'd supposed we did that already. > even though both clauses are technically identical. That's clearly > not a high priority thing to support, but looking at the code it seems > to me that this could be achieved quite simply: just adding a new > operator = in the opclass, with an operator strategy number that falls > back doing exactly what LikeStrategyNumber is doing and that's it. > There shouldn't be any wrong results, even using wildcards as the > recheck will remove any incorrect one. I think you may be overoptimistic about being able to use the identical code path without regard for LIKE wildcards; but certainly it should be possible to do this with not a lot of new code. +1. regards, tom lane
Commits
-
Reword 'simple comparison' => 'inequality' in pgtrgm.sgml
- 7adb8feb0f69 14.0 landed
-
Add missing 'the' to pgtrgm.sgml
- b7edb5d96e7c 14.0 landed
-
Handle equality operator in contrib/pg_trgm
- 935f66665022 14.0 landed