Platform Summary¶
pg_relay does not use LISTEN/NOTIFY — the Processor finds work by polling a durable table — so it works on any managed PostgreSQL service that accepts an ordinary client connection. Connect the Processor using a direct connection or a session-mode pooler; a transaction-mode pooler (for example, PgBouncer in transaction pooling mode) is not supported, because the Processor holds a session-level advisory lock for its instance slot, which needs a connection that stays pinned to the same backend for its whole session. See Connection Poolers in the Technical Guide for the full explanation.
| Platform | Extension install | Admin role | Special consideration |
|---|---|---|---|
| AWS RDS | Not supported | postgres (rds_superuser) |
Connect to the instance endpoint |
| AWS Aurora | Not supported | postgres (rds_superuser) |
Use the cluster writer endpoint (the queue lives there) |
| Azure Flexible Server | Not supported | Admin user (set at creation) | Firewall rules; SSL enforced |
| Google Cloud SQL | Not supported | postgres (cloudsql_superuser) |
Cloud SQL Auth Proxy recommended |
| Generic cloud | Varies | Varies | Point the Processor at the primary/writer |
Continue to Before You Begin for what you need on hand before setting anything up.