Hot take for this Wednesday: for most RAG apps, adding a dedicated vector database on day one is premature infrastructure. If you already run Postgres, pgvector is probably enough. If you already run Elasticsearch or OpenSearch, its vector search is probably enough. Reach for a separate vector store when you have measured a scale, latency, or filtering problem your current database can't handle, not because a "RAG stack" diagram had a box labeled "vector DB."
Embeddings are just another column. The hard part of RAG is usually chunking, retrieval quality, and evals. Where the floats live is rarely the bottleneck.
What "just use Postgres" actually gets you in 2026
This isn't the pgvector of 2023. From the project's own README and changelog:
Two ANN index types. HNSW ("better query performance than IVFFlat (in terms of speed-recall tradeoff), but has slower build times and uses more memory") and IVFFlat (faster builds, less memory, lower speed-recall).
Smaller vectors when you need them.β¦