litellm-proxy-1 | ValueError: Provider 'pg_vector' is not supported for RAG ingestion

[ian-hailey]

I'm trying to use litellm-pgvector as a vector-store with litellm-proxy and have that started in a container along with pgvector-db in another container both along side litellm-proxy. If I try to use the Create Vector Store UI and in step 2 select PostgresSQL pgvector (LiteLLM Connector) as the provider I get error:

litellm-proxy-1 | ValueError: Provider 'pg_vector' is not supported for RAG ingestion

What am I missing?

[krotname]

I think this is a current LiteLLM limitation, not a Docker/container wiring issue.

pg_vector is registered for the vector store API path, but not for the all-in-one RAG ingestion path. In the code, litellm/rag/main.py resolves the provider from ingest_options["vector_store"]["custom_llm_provider"] and then checks INGESTION_REGISTRY. That registry includes several ingestion providers, but not pg_vector. So selecting pg_vector in this RAG ingestion flow leads to the exact error you are seeing: Provider 'pg_vector' is not supported for RAG ingestion.

So the split is roughly:

• pg_vector / litellm-pgvector: available as a compatible vector-store backend for vector store operations/search.
• LiteLLM RAG ingestion UI: currently only works with the providers in the RAG ingestion registry.

Practical workaround: create/populate the pgvector-backed vector store outside that RAG ingestion UI path, then query it through LiteLLM's vector store/search flow. To make the UI ingestion path work with pg_vector, LiteLLM would need a pg_vector ingestion implementation and a registry entry for it.

[omni-front]

"Your issue is that pg_vector is not supported for RAG ingestion in the current LiteLLM version. Modify the ingestion logic to bypass the unsupported path:

if provider == "pg_vector":
    raise ValueError("Provider 'pg_vector' is not supported for RAG ingestion")

This will prevent the unsupported path from being triggered and allow you to handle the ingestion separately."