When does RDS Proxy pay for itself?

When you have many short-lived Lambdas or ECS tasks each opening pools to the same Aurora cluster—Proxy multiplexes application connections onto fewer DB connections. It does not remove the need for query tuning or fix N+1 queries.

Do prepared statements help on RDS?

Yes for repeated OLTP statements—parse/plan once, execute many. ORMs often disable or duplicate prepared statements per pool connection; verify PgBouncer/RDS Proxy transaction vs session pooling mode compatibility.

Connection Pool Exhaustion and Deadlocks on RDS

Database Deadlocks, Connection Pool Exhaustion, and Prepared Statements on RDS

Quick summary: Too many "too many connections" pages are fixed by raising max_connections—which trades one outage for OOM on the writer. This guide traces deadlocks, pool sizing, RDS Proxy, and prepared statement caching on Aurora.

Key Takeaways

This guide traces deadlocks, pool sizing, RDS Proxy, and prepared statement caching on Aurora
June 2026: Aurora PostgreSQL scales with instance class—not with your microservice count
A fleet of 80 ECS tasks × pool size 20 = 1,600 client slots fighting a ~5,000 ceiling on , before autovacuum and admin connections consume headroom
Field note — Logistics SaaS (~$18k/mo Aurora): p99 API 5
2 s during deploy; showed 4,800 connections, mostly from a leaked ORM session

June 2026: Aurora PostgreSQL max_connections scales with instance class—not with your microservice count. A fleet of 80 ECS tasks × pool size 20 = 1,600 client slots fighting a ~5,000 ceiling on db.r6g.xlarge, before autovacuum and admin connections consume headroom.

Field note — Logistics SaaS (~$18k/mo Aurora): p99 API 5.2 s during deploy; pg_stat_activity showed 4,800 connections, mostly idle in transaction from a leaked ORM session. RDS Proxy + pool cap 15/task dropped connections to 620; p99 220 ms. Use RDS max connection calculator.

Deadlock detection

PostgreSQL logs deadlock detected with cycle details. Fix lock order (always lock parent row before child), shorten transactions, avoid user prompts inside transactions.