Full-text search using postgresql #162

Oleg-Komarov · 2024-06-03T19:58:47+02:00

Oleg-Komarov commented

2024-06-03 19:58:47 +02:00

See #127: current search is too naive to be useful.
It does a simple substring match and doesn't do any ranking.

This is an attempt at making search more useful without introducing
more components into the project's infrastructure.

This introduces a discrepancy between sqlite and postgresql support:
sqlite keeps the old unsatisfying implementation.

We don't have any metrics for search quality, but we can reconstruct
search behavior from access logs: we see search terms and page
response size, that can indicate if we found any results.

If further improvements to search are required, we probably should
consider using meilisearch (or alternatives) for indexing.

See #127: current search is too naive to be useful. It does a simple substring match and doesn't do any ranking. This is an attempt at making search more useful without introducing more components into the project's infrastructure. This introduces a discrepancy between sqlite and postgresql support: sqlite keeps the old unsatisfying implementation. We don't have any metrics for search quality, but we can reconstruct search behavior from access logs: we see search terms and page response size, that can indicate if we found any results. If further improvements to search are required, we probably should consider using meilisearch (or alternatives) for indexing.

Oleg-Komarov added 9 commits 2024-06-03 19:58:48 +02:00

use postgres SearchQuery and SearchVector for search 2ff68c4b3e

use rank 867bdd9050

fts + trgm fallback 16e82fde28

Merge branch 'main' into fts 2630953de8

remove condition for local testing 4e9e91791f

fix merge 318ba218ea

cleanup 090a2a6679

add ts_rank 890c96986b

add migration ac52988ea7

Oleg-Komarov added 1 commit 2024-06-03 20:03:15 +02:00

missing part of migration d58bc45158