GoKawiilPrisma pgbouncer setting quadrupled query round-trips on Supabase for six months, KaribuKit finds
KaribuKit, a hotel booking system built by the operator of Mara Hilltop lodge, discovered that a misconfigured 'pgbouncer=true' setting in Prisma's Supabase connection had forced every database query to make four network round-trips instead of one since March. Fixing the setting cut the availability check on the booking page from 8.06 seconds to 1.88 seconds. The discovery came the same night the team also fixed an unrelated crash caused by an image preloader overwhelming memory on mobile Safari.
GoKawiil's interpretation of the reporting above, not reported fact.
The episode shows how a single overlooked connection-pooling flag can silently degrade an entire application's performance for months while engineers chase the wrong explanations, in this case blaming network geography instead of configuration. It's a cautionary example for any team using Prisma with pooled Postgres connections like Supabase's, where subtle parameter mismatches can multiply latency without throwing errors.
- A Prisma pgbouncer=true misconfiguration made every Supabase query take 4 round-trips instead of 1 for six months.
- Fixing the setting reduced a booking availability check from 8.06s to 1.88s.
- The slowdown was initially misattributed to network latency rather than a fixable configuration bug.
Source: blog.simbastack.com, 2026-09-15
Published there as: “Prisma's pgbouncer=true on Supabase made every query 4 round-trips (postmortem)”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.