Prisma's pgbouncer=true on Supabase made every query 4 round-trips (postmortem)
Summary
A postmortem detailing how Prisma's pgbouncer=true setting with Supabase caused every database query to incur four round-trips, leading to significant latency for an availability API. The author traces the issue to the transaction pooler and a misconfiguration, documents measurements and the fix (moving from pgbouncer to a direct connection), and shares practical diagnostic steps and lessons for similar deployments.