22.9k stars · PostgreSQL License · v0.8.x, actively released through 2026 · Track this in Scout
Vector search as an ordinary SQL query inside the Postgres he already runs. No new server, no new backup story.
▶Repo detailsthe review · specs · pros & cons
What it is
A PostgreSQL extension that adds a vector column type and nearest-neighbour search operators. Embeddings become ordinary columns and similarity search becomes an ordinary ORDER BY in a query you already know how to write.
What it is good for. Every "find where in this conversation we discussed X" feature needs vector search, and the tempting path is to bolt on a dedicated vector database. Don't — that is a second server to run, secure, back up and pay for. pgvector keeps the vectors beside the rows they belong to, so one pg_dump still captures everything and a single query can filter by user, document and date and rank by similarity. For a small team, that operational simplicity is worth far more than the last few percent of benchmark speed.
- No new service. One
CREATE EXTENSIONand your existing backups already cover the vectors - Combines similarity with normal SQL filters — something most vector databases make awkward
- Permissive PostgreSQL licence and the de-facto standard, so Claude Code writes it correctly first time
- Building an HNSW index is memory-hungry. Set
maintenance_work_memproperly or it will fall over on a small VPS - At very large scale a dedicated engine wins — though most projects are a long way from that problem
- Index parameters and the embedding model must stay in sync, or search quietly degrades with no error to warn you
pgvector keeps the vectors beside the rows they belong to, so one pg_dump still captures everything and a single query can filter by user, document and date and rank by similarity.
