Hello, reading through migration docs to move from v13 to v14 (https://github.com/Arize-ai/phoenix/blob/main/MIGRATION.m...

·Apr 10, 2026 04:44 PM·

Hello, reading through migration docs to move from v13 to v14 (https://github.com/Arize-ai/phoenix/blob/main/MIGRATION.md). I am a little confused as the changes required for database connection strings. The docs state:

No configuration changes are needed — PHOENIX_SQL_DATABASE_URL continues to work with the same postgresql:// connection strings.

Yet my working configuration defines the following environment variables:

export PHOENIX_POSTGRES_HOST=my.postgresql.server.fqdn
export PHOENIX_POSTGRES_USER="my_phoenix_username"
export PHOENIX_POSTGRES_PASSWORD=my_phoenix_user_password
export PHOENIX_POSTGRES_DB="phoenix"

Is this configuration format no longer supported on v14?

5 comments

· Sorted by Oldest

RunLLM
APP
·
·
Your configuration format using `PHOENIX_POSTGRES_HOST`, `PHOENIX_POSTGRES_USER`, `PHOENIX_POSTGRES_PASSWORD`, and `PHOENIX_POSTGRES_DB` *is still supported in v14*. The migration docs confirm that `PHOENIX_SQL_DATABASE_URL` continues to work, but the environment variable approach you are using is also explicitly documented and supported for PostgreSQL connections in v14 and later. You can use either the connection string (`PHOENIX_SQL_DATABASE_URL`) or the individual environment variables for database configuration—no changes are required for your setup when upgrading from v13 to v14. See <https://arize.com/docs/phoenix/self-hosting/configuration#server-configuration|official configuration docs> and <https://github.com/Arize-ai/phoenix/blob/main/MIGRATION.md|migration notes> for confirmation. Would you like more detail on how Phoenix prioritizes these variables or example configurations? Sources: - <https://arize.com/docs/phoenix/self-hosting/configuration#server-configuration|Phoenix configuration docs> - <https://github.com/Arize-ai/phoenix/blob/main/MIGRATION.md|Phoenix migration guide>
💡 Hint: Mention RunLLM in the thread for followups.
Roger Y.
·
·
Your configuration should continue to work. No user-facing changes were made. The change being noted was the removal of an internal dependency (psycopg).
Peter W.
·
·
thanks! I wasn't sure if PHOENIX_POSTGRES_.. had been deprecated in a prior release and had missed it :)
1
Peter W.
·
·
i can confirm it works too - db migration went through with zero issues 🎉
Roger Y.
·
·
nice. thanks for confirming
💯1