Dedicated Pooler with PgBouncer

[w3b6x9]

Today we’re announcing the official release of Dedicated Pooler - a PgBouncer instance co-located with your Postgres database for lower latency, better performance, and higher reliability.

This is available today for paid plans on the Supabase platform while free and paid plans continue to benefit from our Shared Pooler via Supavisor.

Why Dedicated Poolers

We created Dedicated Poolers to give you the ultimate flexibility in choosing the right connection type for your specific use case.

Now you have three options for connecting to your database and you can mix and match depending on your use case:

1. Direct connections (All Plans): Recommended for when you are connecting using servers.
2. Shared Pooler (All Plans): Recommended for when you are connecting using serverless functions (like Next.js or AWS Lambda) and/or IPv6-only networks.
3. Dedicated Pooler (Paid Plans): Recommended for when you are connecting using serverless functions and you start to scale up. Available on Pro Plan and above.

How It Works

• Dedicated Pooler (IPv6 Only) - Only transaction mode is available. For IPv4-only networks, purchase the IPv4 add on or use the Shared Pooler.
• Shared Pooler (IPv4 + IPv6) - Both transaction and session modes are available. Use this Pooler only for networks that don't support IPv4 or if you need prepared statements.
• Dedicated Pooler Prepared Statement Support (Coming Soon) - We plan to support prepared statements in transaction mode by upgrading all PgBouncer instances to version 1.21+.

Get started by navigating to your project’s Connect settings or learn more about Dedicated Poolers by reading the announcement or going through the docs.