Rider 2024.2 database tools: connection keep-alive and idle timeout options after migrating data sources

Goal

I want to keep Rider's built-in Database tool window reliably connected to a remote PostgreSQL instance during long editing sessions, after moving an existing data source configuration from Rider 2023.3 to 2024.2. The IDE's database tools are based on the JetBrains DataGrip engine, and I am trying to understand which documented settings govern idle connection behavior rather than guessing.

Constraints and uncertainty

The data source works initially, but after the IDE sits idle, the next query or schema refresh appears to stall or require a reconnect. I am unsure whether this is controlled by Rider itself (for example the auto-disconnect and keep-alive options on the data source Options tab), by the JDBC driver's socket/timeout properties, or by server-side idle session limits. I also do not know whether the 2024.x releases changed any defaults in this area compared with 2023.3, so previously tuned settings may no longer behave the same.

Ideally I would like to verify behavior with Rider's database log output rather than trial and error.

Questions

• Which documented Rider data source options (auto-disconnect interval, keep-alive query, driver-level timeout properties) control idle connection lifetime, and what are their defaults in recent 2024.x releases?
• Did the migration of data source settings between major Rider versions ever reset or rename these options?
• What logging or diagnostic output in Rider can confirm whether a stall is a client-side disconnect versus a server-side session termination?