
Pgpool-II
5.8#17 in database proxy softwareFree planFree planLinuxSelf-hosted
Visit
| Fact | Pgpool-II | Supavisor |
|---|---|---|
| Authentication | Supported authentication methods include trust, clear-text password, MD5, SCRAM-SHA-256, certificate, PAM, and LDAP; GSSAPI is not supported. | Client credentials can be verified using tenant user records or an authentication query. |
| High availability | It provides automatic failover, Watchdog for Pgpool-II high availability, quorum, and split-brain prevention. | Cluster nodes monitor tenant pools and reconnecting clients can start replacement pools after a node failure. |
| Purpose | Pgpool-II is middleware between PostgreSQL servers and database clients that relays PostgreSQL protocol messages transparently. | Supavisor is a scalable, cloud-native Postgres connection pooler. |
Pgpool-II suits PostgreSQL administrators who need self-hosted connection pooling, query distribution, or failover capabilities. It also fits teams comfortable configuring and maintaining middleware themselves.
Supavisor suits teams operating PostgreSQL that need connection pooling across tenants or a single-tenant PgBouncer replacement. It is aimed at self-hosted deployments rather than serverless environments.