Search: full-text, pgvector & hybrid (RRF)
"postgres tip" should find a post titled "Tips for indexing Postgres," and "why is my database slow" should find that same post even though it never uses the word "slow." The first is full-text search — matching words. The second is semantic search — matching meaning, via pgvector. DevLog needs both, and the two are combined with a technique called RRF that doesn't compare their scores at all — because a tsvector rank and a cosine distance aren't even the same unit.
try to break it
you drive.
At k = 1, a #1 finish on either signal dominates the sum — "Why Postgres feels slow" wins on the strength of its #1 vector rank alone, even though it barely matches the literal words. At k = 50 the gaps between 1/(51), 1/(56), 1/(59)… are all tiny, so a document that is merely solidly good on both signals(rank 3 + rank 3) overtakes documents that are brilliant on one signal and weak on the other. That smoothing — not chasing a single spiky #1 — is why Supabase's default is rrf_k = 50, not 1.