pgxpool
pgxpool: A Go-embedded pool with lifecycle controls and PostgreSQL-specific features. Ranked #18 of 29 in Database Connection Pooling Software by our editors (7.2/10); pricing: Open source; best for go PostgreSQL services needing lifecycle controls.
At a glance
- Editor score7.2 / 10
- PricingOpen source
- Best forGo PostgreSQL services needing lifecycle controls
- Paid fromFree
- Transaction poolingNo
- Facts checked14 Nov 2026
Where it wins
- Configurable minimum and maximum connections, lifetime, and idle limits
- Health checks and hooks cover connection lifecycle events
- Supports transactions, statement caching, COPY, and LISTEN/NOTIFY
Where it doesn't
- Supports PostgreSQL rather than a range of databases
- Embedded in Go applications, not a standalone proxy or service
- Does not provide transaction pooling
Our verdict on pgxpool
For Go services that connect to PostgreSQL, pgxpool provides a concurrency-safe pool within the pgx driver and toolkit. It reuses connections and gives developers controls over minimum and maximum pool size, connection lifetime, and idle time. Its focus is application-level connection management, making it a fit for teams building PostgreSQL-specific Go applications rather than organizations seeking a separate pooling service.
The package covers more than connection reuse. It includes health checks and ping behavior, along with hooks around connection creation, acquisition, release, and closure. Applications can execute PostgreSQL queries and transactions through the pool, use automatic statement preparation and caching, and access COPY and LISTEN/NOTIFY support. That breadth makes pgxpool useful when a Go service needs pool lifecycle controls alongside PostgreSQL capabilities, without moving pooling into a separate component.
The main trade-off is its narrow, embedded model. pgxpool targets PostgreSQL and runs inside a Go application; it is not a standalone proxy and does not offer transaction pooling. The project is open source, with documentation and community support channels. Choose it when your application is in Go and you want direct control of PostgreSQL connections and their lifecycle. Consider a different approach if you need a database-agnostic pool or a separately deployed pooling layer.
Your product? Our editors can test pgxpool in depth and publish a review, labelled as paid · from $149/mo →
pgxpool pricing
pgxpool fact sheet
| Free plan | Not verified |
|---|---|
| Paid from | Free |
| Transaction pooling | No |
| Pooling modes | Not verified |
| Deployment model | Embedded |
| Supported databases | PostgreSQL |
| Connection limit | Not verified |
| Protocol support | PostgreSQL wire protocol |
| Deployment | Self-hosted |
| Support | Docs, Community |
| Built for | Solo, Small business, Mid-market, Enterprise (editorial estimate) |
| Pricing | Open source |
| Website | github.com |
| Facts checked | 14 Nov 2026 |
Alternatives to pgxpool
- MariaDB MaxScaleSQL-aware pooling and routing for MariaDB and MySQL-compatible production environments.9.3
- OdysseyA focused, open-source pooler for PostgreSQL session and transaction workloads.9.1
- PgBouncerA self-hosted PostgreSQL pooler with flexible modes and connection controls, but no built-in failover.8.9
See all pgxpool alternatives →
Used pgxpool? Be the first to review it
The editor score above is our own research. What this page doesn't have yet is a reader's view — what you used pgxpool for, what worked and what didn't. No stars are seeded and no review is paid for; an editor reads every one before it appears.
Write a reviewTwo minutes · verified accounts only · read by an editor before it appears
Featured on iTechGuides
pgxpool is listed in our Database Connection Pooling Software directory. Add the badge to your site — it links back to this page.
<a href="https://www.itechguides.com/products/pgxpool/"><img src="https://www.itechguides.com/best/badge/pgxpool.svg" alt="Featured on iTechGuides" width="230" height="46"></a>
Reviewed by iTechGuides Editors · Editorial team · Updated Nov 2026
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