17 ms·
That's true for the kernel, How about extensions such as ParadeDB BM25 https://www.paradedb.com/ https://www.paradedb.com/ + PGroonga https://pgroonga.github.io
by Vonng 3y ago
That's true for the kernel, How about extensions such as ParadeDB BM25 https://www.paradedb.com/ https://www.paradedb.com/ + PGroonga https://pgroonga.github.io/ https://pgroonga.github.io/ + PG Bigm https://github.com/pgbigm/pg_bigm https://github.com/pgbigm/pg_bigm ?
- kiwicopple 3y agoalso with pg_trgm[0] (mentioned by OP) and pgvector for semantic search you have a pretty powerful search toolkit. for example, combining them for Hybrid Search [1] [0] https://www.postgresql.org/docs/current/pgtrgm.html https://www.postgresql.org/docs/current/pgtrgm.html [1] Reciprocal Ranked Fusion: https://supabase.com/docs/guides/ai/hybrid-search https://supabase.com/docs/guides/ai/hybrid-search
- mistrial9 3y agothe difference is cached/pre-calc results in a (big on disk, expensive to compute) inverted index.. you cannot beat that at runtime
- jillesvangurp 3y agoStill very limited and frankly all a bit low level primitives. Unless you are a search expert, you won't be able to do much productive with this stuff. If you are, it might fit a few use cases. But then, why limit yourself to just this stuff? The point of that of course being that the target audience for this stuff is actually people that for whatever reason are a bit shy using the right tools for the right job here and are probably lacking a lot of expertise. The intersection of people with the expertise that would be happy with this narrow subset of functionality is just not a lot of people.