From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Supporting = operator in gin/gist_trgm_ops |
Date: | 2020-10-25 11:32:29 |
Message-ID: | CAOBaU_YWwtT7tdggtROacjdOdeYHCz-tmSwuC-j-TOG-g97J0w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello,
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'
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.
Did I miss something? And if not would such a patch be welcome?
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-10-25 14:52:50 | Re: pgstat_report_activity() and parallel CREATE INDEX (was: Parallel index creation & pg_stat_activity) |
Previous Message | Julien Rouhaud | 2020-10-25 11:13:44 | Re: Collation versioning |