litellm - 💡(How to fix) Fix [Bug]: pg_vector cannot add or update llm_params

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Fix Action

Fix / Workaround

Workarounds:

  1. You can still create a pg_vector vector store with the API, but then you also need to create it on pg_vector manually.
  2. Or you can edit the json field in the database after creation.
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

When adding or updating a pg_vector vector store, you cannot update the credentials in the litellm_params map. Instead you find the Metadata field.

Update vector store: <img width="1605" height="804" alt="update" src="https://github.com/user-attachments/assets/fca7cc23-cdee-4660-8b3f-801f9a091a76" /> Here it looks like the metadata and the litellm_params fields are confused with each other. The UI indicates that the Metadata is in fact the litellm_params, but this is not the case when you view it afterwards.

Add Vector store: <img width="1000" height="913" alt="add" src="https://github.com/user-attachments/assets/4cd11582-3ddf-4755-9e8d-443562eac09c" /> Here, the litellm_params is completely missing.


Workarounds:

  1. You can still create a pg_vector vector store with the API, but then you also need to create it on pg_vector manually.
  2. Or you can edit the json field in the database after creation.

Steps to Reproduce

  1. Create/configure a litellm_pg_vector source. 2a. Try to add a vector store 2b. Try to update a vector store

Relevant log output

What part of LiteLLM is this about?

UI Dashboard

What LiteLLM version are you on ?

v1.83.3-stable

Twitter / LinkedIn details

No response

extent analysis

TL;DR

Update the vector store using the API and then manually create or update it on pg_vector, or edit the JSON field in the database after creation to work around the issue with updating credentials in the litellm_params map.

Guidance

  • The issue seems to be related to a UI confusion between the Metadata and litellm_params fields when updating or adding a pg_vector vector store.
  • To verify the issue, try creating or updating a vector store through the UI and then check the actual fields stored in the database or viewed afterwards.
  • As a workaround, use the API to create or update the vector store and then manually ensure the correct configuration on pg_vector.
  • Editing the JSON field in the database after creation is another possible workaround, but this may require direct database access and should be done with caution.

Example

No specific code example is provided due to the nature of the issue being more related to UI and configuration rather than code.

Notes

The provided workarounds suggest that the issue might be specific to the UI interaction with the vector store configuration, and using the API or direct database edits can circumvent the problem. However, these workarounds may not be ideal for all users and could introduce additional steps or risks.

Recommendation

Apply the workaround of using the API for vector store creation or updates and then manually ensuring the correct configuration on pg_vector, as this method is explicitly mentioned and seems to be a reliable, though not ideal, solution to the problem.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

litellm - 💡(How to fix) Fix [Bug]: pg_vector cannot add or update llm_params