The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Hey all, been seeing this error pop up occasionally `<https://sqlalche.me/e/14/e3q8>`

reading through some of the support seems to be an issue with psycopg2? Has that been resolved in the newest version 1.1.20? Currently we are running on 1.1.19 and still having the issue ocassionally.

Hey Scott, do you have a full message / stack trace for the error? I think there are a lot of different issues that could fall under the "OperationalError" umbrella

```
(Background on this error at: <https://sqlalche.me/e/14/e3q8>) Is the server running on that host and accepting TCP/IP connections?
WARNING:root:Retrying failed database connection: (psycopg2.OperationalError) connection to server at "<http://orchestration-prod01-cus-server.privatelink.postgres.database.azure.com|orchestration-prod01-cus-server.privatelink.postgres.database.azure.com>" (10.20.4.148), port 5432 failed: Connection timed out```

Hi, I believe you can configure the connection timeout using `.Values.postgresql.postgresqlParams` on Helm. You can configure a timeout using the `connect_timeout` keyword.

If you’re configuring the `dagster.yaml` yourself, you can configure the `params` key under `postgres_db`

```postgres_db:
  username: ...
  password:
    env: DAGSTER_PG_PASSWORD
  hostname: ...
  db_name: ...
  port: ...
  params: 
    connect_timeout: YOUR_TIMEOUT```

<@U01AV4K3W14> I see the value in teh helm chart but what is supposed to be the default value of that?

<https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNECT-CONNECT-TIMEOUT>

This is a postgres question - unfortunately it doesn’t explicitly say here. Some answers online are saying 30 seconds?