PgBouncer

PgBouncer is a self-hosted pooler for applications that use PostgreSQL. It is a strong fit for teams seeking to reuse database connections and manage the software themselves; its narrow focus makes it less suitable when balancing traffic or failover must be built in.

Overview

By reusing PostgreSQL server connections, PgBouncer reduces the performance impact of repeatedly opening new ones. It can route to destination databases on different hosts, but it does not distribute traffic across those hosts or detect failures. Teams that need either capability must handle it through DNS changes or external tools.

The project dates to 2007 and is distributed as source, with native operating-system packages and dedicated RPM and Debian repositories also offered. Version 1.26.0, released September 23, 2026, fixes three denial-of-service CVEs. Keeping deployments current is therefore an important operational consideration.

Key features

Pooling modes

Session, transaction, and statement pooling give operators different ways to reuse backend connections. Statement pooling disallows multi-statement transactions, which rules it out for applications that depend on them. Transaction and statement modes can track protocol-level prepared statements when max_prepared_statements is non-zero, offering support for that use without changing the restriction on multi-statement transactions.

Authentication and TLS

Authentication options include client certificates, SCRAM-SHA-256, LDAP, PAM, and HBA-based configuration. TLS support depends on building with OpenSSL 1.0.1 or later. This range of documented options suits deployments with varied authentication needs, while TLS adds a build dependency to account for.

Resource use and deployment

The documented default memory requirement is 2 kB per connection, a useful planning figure for connection-heavy deployments. Building requires Libevent 2.0 or later, pkg-config, and a C11-capable compiler; OpenSSL is needed for TLS. Optional integrations include PAM, LDAP, and systemd. Windows is supported, but MinGW is the only documented supported Windows build environment, a meaningful constraint for Windows operators.

Pricing

PgBouncer is free: the PgBouncer plan costs nothing and provides a source release for self-hosted use. There is no free trial because the software is free. This makes it a straightforward option for teams able to run and maintain their own deployment; the tradeoff is that the deployment model is self-hosted rather than a managed service.

Platforms

PgBouncer supports Linux and Windows and is self-hosted. Windows deployments have the additional build-environment constraint of MinGW. Source releases and native OS packages provide different installation paths, with dedicated RPM and Debian repositories also available.

Who it's for

PgBouncer suits PostgreSQL operators who want connection reuse, need to select among session, transaction, and statement pooling, and are prepared to manage a self-hosted tool. It is a weaker fit for applications requiring multi-statement transactions in statement mode, or for teams that expect the pooler itself to balance among backend hosts or handle failover.

Pros and cons

• Pros: Three pooling modes let operators match connection reuse to workload needs.
• Pros: Documented authentication choices include client certificates, SCRAM-SHA-256, LDAP, PAM, and HBA-based configuration.
• Pros: Free self-hosted distribution and a stated default of 2 kB per connection make cost and memory planning more direct.
• Cons: Statement pooling disallows multi-statement transactions, limiting its use with applications that rely on them.
• Cons: There is no internal multi-host load balancing or failover detection, so those needs call for DNS changes or external tools.
• Cons: Building requires several dependencies, and Windows builds are limited to MinGW.

Alternatives

For a broader directory of options, see Database Proxy Software.

• MySQL is an alternative with a freemium model, a free plan, and a free trial.
• OceanBase Database offers a free Community Edition described as an open-source distributed database with full kernel capabilities.
• PgDog has a free open-source plan under AGPL-3.0 and a separate Enterprise plan.
• pgagroal is a free, self-hosted PostgreSQL connection pool, suited to readers considering another tool in the same category.
• PgDoorman is another free, self-hosted option.
• ShardingSphere-Proxy offers a free open-source binary distribution with Docker and Helm deployment.
• TiCDC is a free alternative for readers considering another database tool.
• TurbineProxy offers a free Apache-2.0 open-source plan with no per-query fees.

Verdict

Choose PgBouncer if your priority is free, self-hosted PostgreSQL connection pooling with a choice of three modes. Its focused pooling role is the reason to choose it; the absence of built-in load balancing and failover is the reason to look elsewhere or pair it with other infrastructure.