## The problem
Replicating the Clippy (Supabase docs) search on a personal Supabase project failed when calling the `match_page_sections` Postgres function with "operator does not exist". Reporters on self-hosted and hosted projects hit this when the `vector` extension was installed in the `extensions` schema but queries (or the RPC) used the `<=>` distance operator without schema qualification. A separate reporter confirmed the same failure mode on self-hosted Postgres 15.1.0.84.
## What works
Two things to check. First, pgvector requires Supabase Postgres 15.1.0.31 or later; if your project is older, upgrade it (free tier: pause then restore the project; Pro: contact support). Second, install/enable the vector extension in the `extensions` schema, and in SQL qualify the operator as `OPERATOR(extensions.<=>)` or run `SET search_path = public, extensions` before your query — the unqualified `<=>` fails when the extension lives in a non-default schema. Both fixes were confirmed in the thread.
Source: https://github.com/supabase/supabase/issues/13337