PgBouncer
PgBouncer is a lightweight, open-source connection pooler for PostgreSQL that reduces the overhead of establishing new database connections by reusing a smaller pool of persistent connections on behalf of many client applications.
Definition
PgBouncer is a lightweight, open-source connection pooler for PostgreSQL that reduces the overhead of establishing new database connections by reusing a smaller pool of persistent connections on behalf of many client applications.
Overview
PostgreSQL, like many relational databases, spawns a dedicated backend process for each client connection, which becomes expensive in memory and CPU when an application opens and closes many short-lived connections, such as in a web application with many concurrent requests. PgBouncer sits between applications and PostgreSQL, accepting many lightweight client connections and multiplexing them onto a much smaller pool of actual database connections, dramatically reducing the connection overhead placed on the database server. PgBouncer supports three pooling modes with different tradeoffs: session pooling, where a client keeps its pooled connection for the life of its session; transaction pooling, where a connection is returned to the pool after each transaction, allowing much higher client concurrency; and statement pooling, the most aggressive and restrictive mode. Transaction pooling in particular is widely used because it allows a small number of real database connections to serve a very large number of concurrent application clients. Because PostgreSQL's per-connection cost is a well-known scaling bottleneck, PgBouncer is a near-standard component in production PostgreSQL deployments, often deployed alongside a load balancer, especially for applications using connection-hungry frameworks or serverless architectures where many short-lived processes might otherwise open a large number of direct database connections. It plays a role for PostgreSQL similar to what ProxySQL provides for MySQL or what Vitess provides at larger scale, though PgBouncer focuses specifically on connection pooling rather than broader query routing and caching.
Key Features
- Lightweight connection pooling specifically for PostgreSQL
- Session, transaction, and statement pooling modes
- Dramatically reduces per-connection memory and CPU overhead
- Supports very high client concurrency with few real database connections
- Minimal configuration and small operational footprint
- Widely used with serverless and connection-hungry application frameworks