Runbook

Connection pool exhaustion in PostgreSQL.

Back to Runbooks

Overview

Connection pool exhaustion is a common incident that occurs when an application is unable to create new database connections due to a high number of existing connections. This happens when the application's connection pooling configurations are inadequate and unable to handle the traffic. This incident can lead to degraded application performance or even application failure. To resolve this issue, the application's connection pooling configurations must be optimized to ensure that the connection pool can handle the application's traffic without exhausting its resources.

Parameters

Debug

Check the maximum number of connections allowed in PostgreSQL

Check the current number of connections in PostgreSQL

Check the number of idle connections in PostgreSQL

Check the connection pool size in the application's configuration file

Check the connection timeout setting in the application's configuration file

Check the maximum number of connections allowed by the application's connection pool

Repair

Increase the maximum number of connections allowed by the connection pool to ensure that the pool can handle the application's traffic without exhausting its resources.

Learn more

Related Runbooks

Check out these related runbooks to help you debug and resolve similar issues.