PgDoorman review
A focused PostgreSQL pooler for teams that need Patroni-aware fallback and routing.
Reviewed by iTechGuides Editors · Editorial team · Updated Nov 2026
PgDoorman is a self-hosted PostgreSQL connection pooler written in Rust, designed for teams operating PostgreSQL workloads on Linux or macOS. It sits between applications and PostgreSQL, reusing backend connections through session or transaction pooling. The project supports PostgreSQL 10 and newer, YAML or TOML configuration, and applications built with Go, .NET, Python, and Node.js. Its open-source model suits teams that want to run and manage the pooler themselves rather than adopt a hosted service.
Its strongest fit is PostgreSQL infrastructure using Patroni. PgDoorman provides Patroni-assisted backend fallback and role-based backend routing through patroni_proxy, alongside automatic configuration generation from PostgreSQL. Database-level connection caps with priority eviction add control over connection pressure, while a multithreaded shared pool spans worker threads. Prepared-statement and plan caching are also included. These capabilities make it a practical choice for teams prioritizing connection reuse, failover behavior, and operational control around a Patroni-backed PostgreSQL environment.
Operations are supported through a Prometheus metrics endpoint and an administrative console with operational commands. The published feature set is focused: PgDoorman offers load balancing and automatic failover, but its routing is role-based rather than query-based. It is therefore better suited to teams seeking a PostgreSQL-specific pooler with Patroni integration than to organizations needing broader database coverage or query-aware routing. Teams that want self-hosted control and can operate Linux or macOS infrastructure should consider it; teams requiring query-level routing should look for a different fit.
Questions about PgDoorman
What does PgDoorman run on? Linux and macOS. It runs self-hosted.
What does PgDoorman integrate with? 2 integrations: Patroni and Prometheus.
Who is PgDoorman built for? Small businesses, mid-market companies and enterprises (our editorial estimate).
PgDoorman pros and cons
- Where it wins
- Session and transaction pooling with shared worker pools
- Patroni-assisted fallback and role-based backend routing
- Prometheus metrics, admin commands, and automatic configuration
- Where it doesn't
- Routing is role-based rather than query-based
- Self-hosted deployment requires operational ownership
- Focused on PostgreSQL 10 and newer
PgDoorman fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update