Expert insights on database management, performance optimization, and reliability engineering from industry professionals
Showing 4 of 4 articles
Configure pgBouncer correctly for your PostgreSQL workload. Compare transaction vs session pooling, size your pool correctly, and monitor pool health in production.
PostgreSQL's 5-10MB connection overhead means 500 app servers exhaust your database before a query runs. pgBouncer 2.0 multiplexes thousands of connections into dozens of server connections with improved auth_query and TLS.
Right-size your PostgreSQL connection pool using the (cores*2)+1 formula. PgBouncer configuration, per-user limits, pool saturation monitoring, and transaction mode pitfalls.
Connection exhaustion is one of the most common causes of database downtime at scale. Here is how production teams use PgBouncer and ProxySQL to handle 10,000+ concurrent connections.
Get the latest database insights and expert tips delivered to your inbox.
Subscribe to our RSS feed for instant updates.
RSS Feed