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
According to jackc/pgx#545 pgx can accept multiple Postgres hosts in the format like 2.2.2.2:1,127.0.0.1,4.2.4.2
I assume that temporal passes this to a driver via POSTGRES_SEEDS env variable
Actual Behavior
From the logs I see that temporal sees string like host1,host2 as a single PG host "host1,host2" so fails to connect
temporal | 2024-04-10T12:13:31.205Z ERROR Unable to connect to SQL database. {"error": "dial tcp: lookup temporal-pg-host1,temporal-pg-host2: no such host", "logging-call-at": "handler.go:52"}
Steps to Reproduce the Problem
Get some Postgres cluster in master/replica mode consists of temporal-pg-host1 and temporal-pg-host2 nodes
Modify docker-compose-postgres.yml, comment out postgres container section and set POSTGRES_SEEDS=temporal-pg-host1,temporal-pg-host2
Run docker compose -f docker-compose-postgres.yml up
Specifications
Version: Actual docker composer manifest from the official Github repo
Platform: MacOS, Docker Compose version v2.26.1-desktop.1
The text was updated successfully, but these errors were encountered:
Expected Behavior
According to jackc/pgx#545 pgx can accept multiple Postgres hosts in the format like 2.2.2.2:1,127.0.0.1,4.2.4.2
I assume that temporal passes this to a driver via POSTGRES_SEEDS env variable
Actual Behavior
From the logs I see that temporal sees string like host1,host2 as a single PG host "host1,host2" so fails to connect
Steps to Reproduce the Problem
POSTGRES_SEEDS=temporal-pg-host1,temporal-pg-host2
docker compose -f docker-compose-postgres.yml up
Specifications
The text was updated successfully, but these errors were encountered: