[Bug]: I got error from postgresql pod. when i install using helm chart.

[yongho-chang]

What happened?

I got below error. after install litellm using helmchart
Additionally, the usage page shows 0.

Is this a bug or did I configure it wrong?

env: offline
docker image: litellm-database:v1.80.8-stable.1-patch01
deploy: using helm chart

install command:
helm install litellm . --set global.imagePullSecrets[0].name=scps1-scr-cred --set replicaCount=1 --set postgresql.image.registry=aspcr01-queffmyz.scr.skr-west.scp-in.com --set postgresql.image.repository=serving/bitnami/postgresql --set postgresql.image.tag=16.1.0-debian-11-r25 --set image.repository=aspcr01-queffmyz.scr.skr-west.scp-in.com/serving/litellm-database --set image.tag=v1.80.8-stable.1-patch01 --set imagePullSecrets[0].name=scps1-scr-cred --set global.security.allowInsecureImages=true -n litellm-stg

error:(postgresql db):
postgresql 10:30:54.63 INFO ==> ** Starting PostgreSQL **
2026-01-06 10:30:54.736 GMT [1] LOG: pgaudit extension initialized
2026-01-06 10:30:54.746 GMT [1] LOG: starting PostgreSQL 16.1 on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2026-01-06 10:30:54.749 GMT [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2026-01-06 10:30:54.751 GMT [1] LOG: could not create IPv6 socket for address "::": Address family not supported by protocol
2026-01-06 10:30:54.755 GMT [1] LOG: listening on Unix socket "/tmp/.s.PGSQL.5432"
2026-01-06 10:30:54.771 GMT [147] LOG: database system was shut down at 2026-01-06 10:30:54 GMT
2026-01-06 10:30:54.848 GMT [1] LOG: database system is ready to accept connections
2026-01-06 10:31:34.135 GMT [205] ERROR: relation "LiteLLM_VerificationTokenView" does not exist at character 15
2026-01-06 10:31:34.135 GMT [205] STATEMENT: SELECT 1 FROM "LiteLLM_VerificationTokenView" LIMIT 1
2026-01-06 10:31:34.479 GMT [206] ERROR: relation "MonthlyGlobalSpend" does not exist at character 15
2026-01-06 10:31:34.479 GMT [206] STATEMENT: SELECT 1 FROM "MonthlyGlobalSpend" LIMIT 1
2026-01-06 10:31:34.489 GMT [206] ERROR: relation "Last30dKeysBySpend" does not exist at character 15
2026-01-06 10:31:34.489 GMT [206] STATEMENT: SELECT 1 FROM "Last30dKeysBySpend" LIMIT 1
2026-01-06 10:31:34.503 GMT [207] ERROR: relation "Last30dModelsBySpend" does not exist at character 15
2026-01-06 10:31:34.503 GMT [207] STATEMENT: SELECT 1 FROM "Last30dModelsBySpend" LIMIT 1
2026-01-06 10:31:34.555 GMT [207] ERROR: relation "MonthlyGlobalSpendPerKey" does not exist at character 15
2026-01-06 10:31:34.555 GMT [207] STATEMENT: SELECT 1 FROM "MonthlyGlobalSpendPerKey" LIMIT 1
2026-01-06 10:31:34.563 GMT [206] ERROR: relation "MonthlyGlobalSpendPerUserPerKey" does not exist at character 15
2026-01-06 10:31:34.563 GMT [206] STATEMENT: SELECT 1 FROM "MonthlyGlobalSpendPerUserPerKey" LIMIT 1
2026-01-06 10:31:34.570 GMT [207] ERROR: relation "DailyTagSpend" does not exist at character 15
2026-01-06 10:31:34.570 GMT [207] STATEMENT: SELECT 1 FROM "DailyTagSpend" LIMIT 1
2026-01-06 10:31:34.576 GMT [207] ERROR: relation "Last30dTopEndUsersSpend" does not exist at character 15
2026-01-06 10:31:34.576 GMT [207] STATEMENT: SELECT 1 FROM "Last30dTopEndUsersSpend" LIMIT 1
2026-01-06 10:35:54.834 GMT [145] LOG: checkpoint starting: time
2026-01-06 10:36:23.335 GMT [145] LOG: checkpoint complete: wrote 285 buffers (1.7%); 0 WAL file(s) added, 0 removed, 0 recycled; write=28.311 s, sync=0.145 s, total=28.501 s; sync files=321, longest=0.004 s, average=0.001 s; distance=1997 kB, estimate=1997 kB; lsn=0/1B02590, redo lsn=0/1B02558
2026-01-06 10:45:54.520 GMT [145] LOG: checkpoint starting: time
2026-01-06 10:45:55.548 GMT [145] LOG: checkpoint complete: wrote 11 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=1.009 s, sync=0.002 s, total=1.028 s; sync fi les=7, longest=0.001 s, average=0.001 s; distance=2 kB, estimate=1798 kB; lsn=0/1B02F50, redo lsn=0/1B02F18

Relevant log output

What part of LiteLLM is this about?

SDK (litellm Python package)

What LiteLLM version are you on ?

v1.80.8-stable.1-patch01

Twitter / LinkedIn details

No response