Connection management for Aiven for PostgreSQL®

Manage connection limits, idle connections, and TLS versions for your Aiven for PostgreSQL® service.

How these settings interact

Keep-alive timeouts and idle_in_transaction_session_timeout guard against different problems, and one doesn't substitute for the other. Keep-alives detect a client that has disconnected at the network level. A client that's still connected, but has left a transaction open, passes every keep-alive probe while it continues holding locks and memory, the scenario covered in Troubleshoot out-of-shared-memory errors.

Before you troubleshoot a connection issue

• Determine whether you're near your plan's max_connections limit before investigating further.
• Confirm clients use scram-sha-256 password encryption and a supported TLS version.
• If the service becomes unresponsive with out of shared memory errors, look for stuck idle in transaction sessions before adjusting connection limits.

Related pages

• Connection limits per plan for Aiven for PostgreSQL®
• Keep-alive connections parameters
• Troubleshoot out-of-shared-memory errors