Pgpool-II

Azure Databases 1 variation

Pgpool-II, a connection pooler for PostgreSQL, fronting a bundled PostgreSQL database and ready to accept pooled connections the moment it boots.

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Variations

This product is available in the build below. Open it for the operating system, cloud and version detail, or read its deployment guide.

ProductCloudOperating systemVersion
Pgpool-II Connection Pooler with PostgreSQL 18 on Ubuntu 24.04 LTS Azure Ubuntu 24.04 18 View · Guide

Overview

Pgpool-II is an open source connection pooler and middleware for PostgreSQL, maintained by the PgPool Global Development Group. It sits in front of the database and keeps a small set of backend connections open, handing them to clients as they arrive and reusing them afterwards, so the database sees a stable, bounded number of connections no matter how many clients turn up. PostgreSQL gives every client its own backend process, which makes connection heavy applications, serverless functions and multiple application servers exhaust the connection limit long before they exhaust CPU or memory.

This appliance bundles Pgpool-II together with a ready to run PostgreSQL database on a single machine. Clients speak the ordinary PostgreSQL wire protocol to the pooler, so any driver, ORM or framework connects unchanged, and the database itself stays on the loopback interface with the pooler as the only way in. Connection pooling is enabled; load balancing and replication are not, because there is a single local backend, and the deployment guide documents how to add remote backends later.

Why the cloudimg image

cloudimg ships Pgpool-II and PostgreSQL preconfigured on a hardened, fully patched base, with the pooler requiring encrypted connections and a password unique to each instance. No database cluster is baked into the image at all: every instance creates its own on first boot and generates its own superuser password, application role password, pooler key material and TLS certificate, so no two deployments share an identity. A built in self test proves the pooling works on your own instance, and a paired deployment guide and 24/7 support are included.

Common uses

  • Connection pooling for high concurrency apps
  • Application databases
  • Serverless and function backends