A database connection is an active communication session between a client and a PostgreSQL server. More allowed connections do not automatically improve application performance: excessive concurrency can overload a modest server, increasing latency while throughput stagnates. section 6.3
The 2,000-connection mistake
A configuration with max_connections = 2000 may appear generous, but a pgbench run with 2,000 clients processed 352.1 transactions per second at 5,535 ms average latency. With 32 clients, latency fell to 55.9 ms, showing that the high-concurrency workload traded responsiveness for a throughput plateau. section 6.3
Use connection limits as an operational control, not as a capacity contest:
- Test client counts against both throughput and latency; throughput alone can hide an overloaded server. section 6.3





