Supavisor pool size limits: sizing the pooler versus enforcing client-side connection caps
On a Supabase project fronted by Supavisor, I need to decide how to handle intermittent connection pool exhaustion during bursty traffic. The workload includes serverless functions that each open their own connections through the transaction-mode pool on port 6543, plus a few long-lived services using session mode on port 5432. The documented trade-off is un
supabase