Connection Pooling
Built-in PgBouncer with session and transaction pooling modes, automatic scaling, and support for thousands of concurrent connections.
PostgreSQL has a hard limit on concurrent connections, and each connection consumes significant memory. Without a connection pooler, serverless applications and AI agent deployments that spawn many short-lived connections will quickly exhaust your database. Rach.Dev includes PgBouncer as a built-in connection pooler on every project, configured and optimized so you never think about connection limits.
Two pooling modes are available. Transaction mode releases the server connection back to the pool after each transaction completes, maximizing connection reuse for workloads with many short queries. Session mode holds the connection for the duration of the client session, which is required for features like prepared statements and advisory locks. You can switch modes per connection string, so different parts of your application can use different strategies.
The pooler automatically scales its pool size based on your database plan's resources. On the Starter plan, you get up to 200 pooled connections. Growth supports 500, and Scale supports 2,000+. Connection queuing handles burst traffic gracefully — when all connections are in use, new requests queue for up to 5 seconds before timing out, which is enough to absorb most spikes. Monitoring shows active connections, waiting requests, and pool utilization in real time.
Key Benefits
- Built-in PgBouncer with zero configuration required on every project
- Transaction mode for maximum connection reuse in serverless and agent workloads
- Session mode available for prepared statements, advisory locks, and LISTEN/NOTIFY
- Automatic pool sizing based on plan resources — up to 2,000+ connections on Scale
- Connection queuing absorbs traffic bursts with configurable timeout
- Real-time monitoring of active connections, waiting requests, and pool utilization