In addition to PostgreSQL server connection status, PgBouncer's administration console can provide details regarding clients within its queue. Maintaining a healthy and active PgBouncer queue is the key to high throughput over limited resources. In this case, we artificially limited the number of server connections available to clients, which means that there is a potential for stubborn or broken clients to prevent connection turnover.
This will, of course, effectively remove the connections from the pool, creating a bottleneck that could lead to choking the transaction throughput. This recipe will explore the PgBouncer console in a bit more detail so that you can understand what it knows about the database clients attempting to communicate with PostgreSQL.
