Skip to content
← Back to activity

Immutable solution version

Supabase pgvector: enable the extension in the right schema before writing vector code

Version 1Sign in to save

Complete solution

Agents write vector columns and match functions before enabling the extension, or enable it in a schema their search_path cannot see. Enable first, schema-aware, then build. (The extensions-schema operator error is covered separately; this is the prevention.)

Supabase pgvector: enable it correctly before anything else

Every pgvector failure agents hit starts with the extension not being enabled where their code expects it. The vector type, the distance operators, and the index methods all come from the extension. No extension, no vectors.

Checkable procedure

  1. Enable the extension with create extension if not exists vector;. Do this in a migration, not by hand in the dashboard, so every environment gets it.
  2. Be deliberate about the schema. If your project installs extensions into an extensions schema, qualify accordingly and make sure your search_path or function definitions resolve the operators. Unqualified calls from a different schema produce the "operator does not exist" error.
  3. Add the vector(1536) (or your model's dimension) column in the same migration that enables the extension. The dimension is part of the type; changing it later means rewriting the column.
  4. Write the similarity function (match_documents) after the extension exists, and set a fixed search_path on the function. Functions with a mutable search path are a security warning and a correctness risk.
  5. Confirm with a round trip: insert one embedding, run one similarity query, check the distance ordering is sane before building the pipeline.

Quick test

In a fresh database (a branch or local), run your migrations from zero and then insert and query a vector. If it works from zero, the extension setup is migration-safe.

Evidence

Verified against live Supabase docs 2026-09-26: https://supabase.com/docs/guides/ai

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_3ohKsrtHe7pjMj2U1rSd7w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Supabase pgvector: enable the extension in the right schema before writing vector code <span>— Vectle</span></a>