Prisma's pgbouncer=true on Supabase made every query 4 round-trips (postmortem)
Prisma's recent postmortem reveals that enabling the pgbouncer=true setting on Supabase caused each database query to perform four round-trips, significantly slowing performance. The issue stemmed from how Prisma's connection pooling interacted with Supabase's PgBouncer configuration, leading to excessive latency. The team identified the root cause, applied a fix, and updated documentation to prevent recurrence in the production environment.