// troubleshooting guide · pgvector
How to Enable pgvector on Supabase
- Status
- Fixed in latest version
- platforms:
- Supabase
- updated:
- November 15, 2026
- reports:
- 2
- Method
- how we research
RUNBOOK · pgvector/enable-pgvector-supabase3 FIXES
// quick answer
Enable vector on the Extensions page or run create extension vector with schema extensions. Dimension must match your model.
Most likely fix: Dashboard
How to fix it
// try these in order, the most common fix is first
FIX 1Dashboard
- 01Database > Extensions
- 02Search for vector and enable it
Did this fix it?FIX 2SQL
- 01Run create extension vector with schema extensions;
- 02Create a column such as extensions.vector(384) matching your model
Did this fix it?FIX 3Filtering
- 01For filtered queries use iterative index scans as the docs suggest
Did this fix it?
Symptoms
Unsure how to turn on vectors in a Supabase project.
Why it happens
- C-01Extension not enabled
- C-02Dimension mismatch with model
// this guide also covers
- enable pgvector supabase
- supabase vector extension
- supabase create extension vector
Still not working?
If pgvector keeps failing, you're not alone. See every pgvector problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usOther pgvector errors
- pgvector Error: extension "vector" is not available
- pgvector HNSW Index Build Slow
- pgvector "operator does not exist: vector <=>" Error
- pgvector Dimension Limit: Cannot Index More Than 2000 Dimensions
- pgvector "different vector dimensions" Error
- pgvector Query Returns Fewer Results Than LIMIT With Filter
- pgvector Index Not Being Used
- pgvector HNSW Build Out of Memory or Shared Memory Error