Timeout on Postgresql connections in dev environment after 3 min

[KristianWood]

Whenever I build the ClimateCube in our dev environment 3 times out of 4 one of two tables will time out after 3 min. The tables are DocumentChatEmbeddingProcess and PL2, and in both cases when they time out its after 3 min, but when they don't time out it takes longer than 3 min. 

I have set the timeout in Sisense.Connectors.PostgreSqlConnector.dll.config to  <add key="Timeout" value="900" /> but this makes no difference

The error I get when the build fails is:

"A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond"

[DRay]

Hi @KristianWood,

Thank you for reaching out.

Are you able to see the performance of the target database? It may not be returning the query quickly enough.

[martinphilip]

In a development environment, encountering timeouts on PostgreSQL connections after three minutes may stem from various factors. DirecTV cable and internet bundles These can include network latency, server load, or misconfigurations. Investigate connection settings, such as the idle_in_transaction_session_timeout parameter, which might be causing premature disconnections. Adjusting this parameter or reviewing network configurations could potentially alleviate the issue, ensuring seamless database interactions during development.