Neon adds hybrid vector and full-text search for agent workflows
matei_zaharia · x · 2026-07-21
Neon says it has made Lakebase Search available, adding hybrid vector and full-text search for agent workflows.
The post explains why the team built lakebasetext and argues that Postgres' default BM25 approach is not enough for this use case. The accompanying diagram contrasts tsrank in GIN with Lakebase BM25, highlighting three differences:
- BM25 uses corpus-wide IDF, so rare terms score higher.
- It adds length normalization so long documents are not unfairly boosted.
- Scores remain more stable as the corpus grows.
The key point is that retrieval for agents needs more than simple term frequency ranking; it needs a search layer designed for scale and relevance.
Related event: Neon Launches Lakebase Search for AI Agent Workflows(2 posts)→
More from coding & agent
- agents-best-practices: a provider-neutral Agent Skill for designing and auditing agentic harnesses — tom_doerr · 2026-09-11
- Cognition's SWE-2 uses a KKT duality argument in RL to shift the effort Pareto curve — YouJiacheng · 2026-09-11
- First-ever Three.js Conference lands in Paris, with a panel on AI-shortened design workflows — OdinLovis · 2026-09-11
- Data engineering, not agent frameworks, is the real bottleneck for enterprise AI agents — dhruv2038 · 2026-09-11
- RTK Terminal Compression Cuts Tokens but Leaves Your AI Coding Bill Unchanged — Bartaseth · 2026-09-11
- GPT-6 Astra beats Factorio with enemies in 44 in-game hours at ~$4,500 API cost — liminal_bardo · 2026-09-11