Public Hostname for the PostgreSQL Connection Pooler
The transaction-mode connection pooler can now be reached from outside the platform, which is what serverless functions and short-lived workers need.
What's changed
- Enable public access for the pooler separately from the direct connection; each keeps its own hostname and ports
- One pooler hostname serves two ports: one for the writer and one that accepts any node
- Pooler ports come from their own ranges, so enabling them never competes with the direct connection ports
- The reader pooler endpoint remains internal-only