You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unable to start ZEP using dedicated Postgres database user with limited access rights (for example, in case of Google Cloud SQL).
Main issues is: ZEP is unconditionally trying to create/update pgvector extension at startup:
when this is not needed because it is already up-to-date
when there are no rights to do that (extensions must be installed by PG DB admin ONLY and not the target applications)
Expected behavior
ZEP can try to create/update an extension if really wants but this should be a warning and not the fatal error. The best way is to check that there is extension already installed.
Logs
time="2023-10-16T11:45:00Z" level=warning msg=".env file not found or unable to load. This warning can be ignored if Zep is run using docker compose with env_file defined or you are passing ENV variables."
time="2023-10-16T11:45:00Z" level=info msg="Starting Zep server version 0.15.1-e950fff (2023-10-13T00:38:11+0000)"
time="2023-10-16T11:45:00Z" level=info msg="Log level set to: info"
time="2023-10-16T11:45:01Z" level=info msg="error enabling pgvector extension: error updating pgvector extension: ERROR: must be owner of extension vector (SQLSTATE=42501)"
time="2023-10-16T11:45:01Z" level=fatal msg="Failed to connect to database: error updating pgvector extension: ERROR: must be owner of extension vector (SQLSTATE=42501)\n"
Environment (please complete the following information):
Unable to start ZEP using dedicated Postgres database user with limited access rights (for example, in case of Google Cloud SQL).
Main issues is: ZEP is unconditionally trying to create/update
pgvector
extension at startup:Expected behavior
ZEP can try to create/update an extension if really wants but this should be a warning and not the fatal error. The best way is to check that there is extension already installed.
Logs
Environment (please complete the following information):
Additional context
Previous version (0.12.4) was working fine in this environment.
The text was updated successfully, but these errors were encountered: