Skip to main content
Connection pooling puts PgBouncer in front of your service. Many client connections share a smaller number of database connections, which reduces load on PostgreSQL and helps applications that open lots of short-lived connections, such as serverless functions and busy web apps. Open a service and go to the Pooler tab.

​
Enable connection pooling

  1. Click Enable Connection Pooling.
  2. Choose a Pool Mode.
  3. Set the number of PgBouncer instances, from 1 to 3.
  4. Optionally set Max client connections (10 to 10,000, default 100) and Default pool size (1 to 1,000, default 20).
  5. Click Enable Pooling.
The Enable Connection Pooling dialog

​
Pool modes

Setup usually takes under a minute. The page shows Connection Pooling Starting until every instance is ready.

​
Connect through the pooler

Once pooling is active, the Pooler tab shows the Endpoint and Port to use.
The Pooler tab showing pooling active with the endpoint and port
Point your application at the pooler endpoint instead of the service host, using the same database name, username and password:

​
Change pooling settings

To change the pool mode or limits, click Disable Pooling, then enable it again with the new settings.

​
Disable connection pooling

Click Disable Pooling and confirm. Applications connected through the pooler are disconnected, so switch them to the service host first.
Pooling must be turned off before a service can be deleted. The delete dialog offers a Turn off pooling button for this.