PgBouncer
pgbouncer.org
- Free plan
- Windows
- Linux
- Self-hosted
What PgBouncer is
PgBouncer is a free, self-hosted connection pooler for PostgreSQL. It reuses server connections to reduce the performance impact of opening new connections, with session, transaction, and statement pooling modes. Statement pooling disallows multi-statement transactions. The tool can route to databases on different hosts, but does not provide internal multi-host load balancing or failover detection. Its FAQ describes DNS round-robin or external TCP load balancers for distributing connections, and DNS reconfiguration or external tools for failover. PgBouncer can track protocol-level prepared statements in transaction and statement pooling when max_prepared_statements is non-zero. Documented authentication options include client certificates, SCRAM-SHA-256, LDAP, PAM, and HBA-based configuration. The features page lists default memory requirements of 2 kB per connection. Source releases are available, alongside references to native packages and dedicated RPM and Debian repositories. Building requires Libevent 2.0 or later, pkg-config, and a C11-capable compiler; OpenSSL is needed for TLS. Windows builds are documented, with MinGW as the only supported Windows build environment.
Who it suits
PgBouncer suits teams running PostgreSQL that want to reuse server connections through a self-hosted pooler. It may suit operators comfortable handling load balancing and failover separately.
Good to know, and what to watch
- Supports session, transaction, and statement pooling.
- Can route to databases on different hosts.
- Documents several authentication options.
- Default listed memory requirement is 2 kB per connection.
- Statement pooling disallows multi-statement transactions.
- No internal multi-host load balancing is provided.
- No internal failover-host configuration or detection is provided.
- Windows builds require MinGW.
Plans
Every plan and pricePgBouncer
Free plan
The verdict
PgBouncer provides PostgreSQL connection pooling with multiple modes and documented authentication choices. Plan separately for load distribution and failover if those are required.
What the maker publishes
- Authentication
- Documented authentication options include client certificates, SCRAM-SHA-256, LDAP, PAM, and HBA-based configuration. source
- Backend hosts
- PgBouncer can route to destination databases on different hosts and is not tied to one backend server. source
- Build dependencies
- Building requires Libevent 2.0 or later, pkg-config, and a C11-capable compiler; OpenSSL is needed for TLS support. source
- Distribution
- The downloads page offers source releases and points to native OS packages and dedicated RPM and Debian package repositories. source
- Failover
- PgBouncer does not provide internal failover-host configuration or detection; its FAQ describes DNS reconfiguration and external tools as options. source
- Founded
- 2007 source
- Integrations
- Optional build integrations include PAM, LDAP, and systemd support. source
- Load balancing
- PgBouncer has no internal multi-host load-balancing configuration; its FAQ describes using DNS round-robin or an external TCP load balancer such as HAProxy or LVS. source
- Memory
- The features page lists default memory requirements of 2 kB per connection. source
- Operating systems
- The installation page documents running PgBouncer on Windows and specifies MinGW as its only supported Windows build environment. source
- Pooling modes
- It supports session, transaction, and statement pooling, with statement pooling disallowing multi-statement transactions. source
- Prepared statements
- It can track protocol-level prepared statements in transaction and statement pooling when max_prepared_statements is non-zero. source
- Purpose
- PgBouncer is a PostgreSQL connection pooler that reuses server connections to reduce the performance impact of opening new connections. source
- Release and security
- The homepage says version 1.26.0, released September 23, 2026, fixes three denial-of-service CVEs. source
- TLS
- The installation documentation lists OpenSSL 1.0.1 or later as a build dependency for TLS support. source
Checked against the maker's pages on 3 Oct 2026.