On Sat, Jan 4, 2025 at 12:16 PM James Addison <jay@jp-hosting.net> wrote:
In the context of considering writing a patch: would the complexity of implementing such a feature for PostgreSQL be worth the potential performance benefits?
Probably not. As Tom said, this sounds like it should be tried as an extension.
And either way, is there more I should learn about and consider? How would I provide convincing supporting evidence if I do write a patch?
As this is the performance mailing list, it might help to describe the real-world problem being encountered here. There are other ways to solve this particular issue. Among them would be using OR not AND in your contrived example, using partial indexes, using pg_trgm, using regular expressions ( i.e. WHERE value ~ '(known|suffix)' ), redesigning your table and/or queries, and outsourcing the searching of large strings to a system more suitable for it.
