Ross ROSS = Recommend OSS · open-source software intelligence for agents

pgbouncer/pgbouncer

lightweight connection pooler for PostgreSQL observed · 2026-08-28

github.com/pgbouncer/pgbouncer · homepage · C · NOASSERTION (other) observed · 2026-08-28

Health v2 · maintenance only

85/100

  • Activity 98
  • Release rhythm 59
  • Longevity 100

Flags: no_license

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 125.5
  • age_days: 5965
  • days_rel: 117
  • days_push: 14
  • n_releases_24m: 5

Full methodology

Adoption not part of the score

4339 stars · 592 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

PgBouncer is a lightweight connection pooler for PostgreSQL that acts as a proxy server, accepting client connections and reusing a smaller pool of backend database connections. It supports session, transaction, and statement pooling modes, TLS, and multiple authentication backends (SCRAM, LDAP, PAM), with low memory overhead and online reconfiguration.

Use cases

  • pool postgres connections for a high-traffic web app
  • reduce postgres max_connections by fronting the database with a pooler
  • pool database connections from many short-lived serverless functions
  • deploy a lightweight pgbouncer sidecar next to my app
  • reuse database connections across microservices
  • upgrade postgres without dropping client connections
  • load balance queries across several postgres servers via dns round-robin

When to choose

  • your application opens many connections and exhausts PostgreSQL's max_connections
  • you need low-overhead, battle-tested connection pooling with minimal memory footprint
  • you want session, transaction, or statement pooling modes with online restart and reconfiguration
  • you need TLS, SCRAM, LDAP, or PAM authentication in front of PostgreSQL

When to avoid

  • you need built-in multi-host load balancing, failover detection, or query routing - PgBouncer relies on external tools like HAProxy or DNS
  • your application depends on session-level PostgreSQL features (LISTEN/NOTIFY, SET, prepared statements) under transaction pooling
  • you need a full database proxy with query analysis, sharding, or read/write splitting

Facets

service · maturity stable

database caching proxy auth security databases backend self-hosted windows bsd cross-platform self-hosted postgresql connection-pooling database-proxy c tls scram-authentication ldap pam devops linux macos docker

6 sources

Member repositories

RepositoryRoleHealth v2
pgbouncer/pgbouncermain85

For agents

markdown · JSON · MCP: product_card(name="pgbouncer/pgbouncer")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem