Philipinho 18222d1142 fix(base): escalate fuzzy filter and search counts to capped-exact ...

Postgres has no per-expression stats for `cells->>'uuid' ILIKE '%…%'`,
`search_text ILIKE`, or `search_tsv @@`, so EXPLAIN Plan Rows falls
back to a default selectivity and is off by orders of magnitude — a
contains filter on a 10k-row base was reporting ~150 against thousands
of real matches. Auto-route any request whose filter tree contains a
contains/ncontains/startsWith/endsWith op or a search term to the
capped-exact path, even when the caller asked for an estimate.

2026-04-25 01:05:02 +01:00

..

client

perf(base): batch page-cell resolution via microtask loader

2026-04-24 12:11:41 +01:00

server

fix(base): escalate fuzzy filter and search counts to capped-exact

2026-04-25 01:05:02 +01:00