How to fix Postgres error "operator does not exist" using pgvector

TL;DR

For "operator. It seems that PostgreSQL cannot find this operator for the vector type provided by the pgvector extension. Detailed Log message:": i finally found the problem; you have to install pg_vector on the extensions schema. Just manually enable the extension in database tab.

operator. It seems that PostgreSQL cannot find this operator for the vector type provided by the pgvector extension. Detailed Log message:

Steps

1. I finally found the problem; you have to install pgvector on the extensions schema. If you are following https://github.com/supabase/supabase/blob/master/supabase/migrations/20230126220613doc_embeddings.sql. Most likely you wont get it work for some reason. Just manually enable the extension in database tab.

2. Postgres function:...

## When to use

You are seeing this: If you are following https://github.com/supabase/supabase/blob/master/supabase/migrations/20230126220613_doc_embeddings.sql. Use this skill when you run into "How to fix Postgres error "operator does not exist" using pgvector".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Variants

Other phrasings of the same problem that show up in reports:

### `` Failed to match page sections: {"code":"42883","details":null,"hint":"No operator matches the given name and argument

```text
``` Failed to match page sections: {"code":"42883","details":null,"hint":"No operator matches the given name and argument types. You might need to add explicit type casts.","message":"operator does not exist: extensions.vector extensions.vector"} ```

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/supabase/supabase/blob/master/supabase/migrations/20230126220613docembeddings.sql

Source: Stack Overflow #75904637 (accepted answer, 3 votes): I have a Postgres function to find the top 10 most relevant vectors. I called this function from a supabase serverless function, but logs returned 500. The error I get is related to the ` operator. It seems that PostgreSQL cannot find this operator for the vector type provided by the pgvector extension. Detailed Log message: Failed to match page sections: {"code":"42883","details":null,"hint":"No operator matches the given name and argument types. You might need to add explicit type casts.","message":"operator does not exist: extensions.vector extensions.vector"} `` Postgres function:...

Verified resolution: I finally found the problem; you have to install pgvector on the extensions schema. If you are following https://github.com/supabase/supabase/blob/master/supabase/migrations/20230126220613doc_embeddings.sql. Most likely you wont get it work for some reason. Just manually enable the extension in database tab.

Source URL: https://stackoverflow.com/questions/75904637/how-to-fix-postgres-error-operator-does-not-exist-using-pgvector