Pyyan / Compare / pgvector vs Qdrant vs Milvus vs Weaviate
pgvector vs Qdrant vs Milvus vs Weaviate
4 of 5Vector Databases · verified 13 Aug 2026
| Specification | pgvector | Qdrant | Milvus | Weaviate |
|---|---|---|---|---|
| Summary | Vectors inside the database you already run. | The fastest of the purpose-built stores. | Built for billions of vectors. | Hybrid search with batteries included. |
| Index | HNSW, IVFFlat | HNSW | HNSW, IVF, DiskANN, GPU | HNSW |
| Hybrid search | Yes, with SQL | Yes | Yes | Yes, native |
| Hosting | Self-host or any managed Postgres | Self-host and managed | Self-host and managed | Self-host and managed |
| Licence | PostgreSQL | Apache 2.0 | Apache 2.0 | BSD-3 |
| p50 latency | ~15ms | 4ms | ~10ms | ~12ms |
| Category | Vector Databases | Vector Databases | Vector Databases | Vector Databases |
| Official | PostgreSQL ↗ | Qdrant ↗ | Zilliz ↗ | Weaviate ↗ |
Highlighted rows are where these differ.
pgvector
- One database for vectors, rows and joins
- The honest default: reach for something else only when this stops working
Best for almost everyone, until scale says otherwise.
Qdrant
- Written in Rust; 10 to 25% faster than Weaviate or Milvus on common workloads
- Strong filtering alongside vector search
- Self-host or managed, same engine
Best for latency-sensitive retrieval.
Milvus
- Distributed architecture with GPU index support
- Heavier to operate than the alternatives
Best for very large corpora.
Weaviate
- Vector, BM25 and metadata filters in one query
- Modules for embedding generation built in
Best for hybrid keyword and semantic search.