pgvector Problems & Issues
Real user-reported problems, complaints, and limitations for pgvector. Based on analysis of 11 signals.
Overall score: 74/100
Issues by Category
HNSW index build is very slow once the graph outgrows memory
The docs say builds are much faster while the graph fits in maintenance_work_mem and Postgres logs a notice when it no longer does. Users report long builds on big tables and need to raise memory and parallel workers.
Filtered vector search returns fewer rows than LIMIT
Approximate indexes apply filters after the index scan. With ef_search 40 and a filter matching 10 percent you get about 4 rows. Iterative scans in 0.8 and partial indexes are the fixes.
Recall drops and memory grows at tens of millions of vectors
Index memory competes with the rest of Postgres, so large workloads need bigger instances. Many teams then evaluate dedicated vector databases for scale.
Queries do a sequential scan and ignore the vector index
The planner only uses the index for ORDER BY on a bare distance operator, ascending, with LIMIT, and with a matching operator class. Wrapped expressions silently fall back to a full scan.
Vectors over 2,000 dimensions cannot be indexed
Storage allows up to 16,000 dimensions but HNSW and IVFFlat on vector stop at 2,000, so 3,072-dim embeddings fail at CREATE INDEX. halfvec raises the index limit to 4,000.
operator does not exist: vector <=> unknown or real[]
The distance operators need a vector on both sides. Untyped parameters or plain arrays from drivers and ORMs fail until you cast to vector or register the driver adapter.
Dimension mismatch errors when you change embedding model
The column is fixed width, so inserting 768 values into a 1536 column fails. n8n, LlamaIndex and OpenAI forum users hit it and must re-embed or add a new column.
IVFFlat gives poor results when built on little data
Docs advise building IVFFlat after loading data and sizing lists from row count. Built too early it returns weak recall until probes are raised.
pgvector error: extension "vector" is not available
The extension is named vector, not pgvector, and the server package must match your Postgres major version. Reports from Fly.io, Railway, DigitalOcean and Vultr threads show the control-file error after upgrades or on hosts that do not ship it.
HNSW build fails on shared memory or runs out of RAM
Parallel builds in Docker need more than the default 64 MB /dev/shm, and a Cloud SQL thread reports failures on pgvector 0.8.0. Real OOM kills come from graph memory.
Extension availability and version lag differ by managed host
Supabase and Neon let you enable it in a click or one SQL line; Railway and Vultr threads show templates without it. Neon supports the latest version plus one behind.
Regret Patterns
Common reasons users regret choosing pgvector.
Embedding model changed after launch
The fixed-width column rejects new vectors, so you re-embed everything or add a new column.
Index built before sizing memory
HNSW build crawls or fails once the graph exceeds maintenance_work_mem.
Filters hurt recall
Filtered queries return too few rows until iterative scans or partitioning are set up.
3,072-dim embeddings cannot be indexed
Index creation fails above 2,000 dimensions for vector.
Free tier too small for indexes
Small RAM and 500 MB or 1 GB storage limits fill quickly with embeddings.
When pgvector Breaks Down
Specific scenarios where pgvector fails or underperforms.
Tens of millions of vectors on one instance
Index memory competes with the rest of Postgres and recall tuning gets harder.
Highly selective metadata filters
Few rows match so approximate scans return too little.
Index builds in a small Docker container
Default shared memory is too small for parallel HNSW builds.
Postgres major upgrade
Extension files for the old version are missing and vector.control is not found.
Free-tier project idle for a week
Supabase Free projects pause after 1 week of inactivity; Neon scales to zero after 5 minutes.