Managing Idle Sessions ​

The database proactively closes both idle sessions and idle transactions within sessions when they reach a timeout limit. You can modify the default settings of the following configuration parameters in order to avoid running out of connections (the maximum number of user connections for the cluster is 2000). These parameters may also help you avoid problems where the presence of idle sessions or idle transactions within sessions holds up background maintenance operations. When these operations are blocked, database storage may reach capacity.

• idle_session_timeout: how long any user session may remain idle before being disconnected.
• idle_in_transaction_session_timeout: how long any transaction within any user session may remain idle before being disconnected.

Note: Running show idle_session_timeout or show idle_in_transaction_session_timeout as a superuser will always return unlimited (0), which is the superuser's setting, not the default setting for the cluster.

Both parameters accept settings with the following units: ms, s, min, h, and d.