Prisma's pgbouncer=true on Supabase made every query 4 round-trips for six months
Prisma's pgbouncer=true on Supabase made every query 4 round-trips (postmortem)
A guest's booking crash led us to a six-month-old database misconfiguration. Prisma's pgbouncer=true flag against Supabase's transaction pooler wrapped every query in four statements, each crossing the 47 ms Helsinki–Dublin link. We had measured the cost on day four, done the arithmetic correctly, and blamed geography. Switching to session mode cut availability checks from 8.06 s to 1.88 s. The fix was one line.
Right arithmetic, wrong sentence. Nobody measured the latency.
- ProjectBarks
> "The uncomfortable part is that the fix already existed. Claude Code, Anthropic's command-line coding agent".
It sounds like there could be something extremely interesting in this article, but the writing style is really off-putting.
> "on staging first and then on production at 23:40"
Why does the reader need to know the exact minute-to-minute timeline?
- tecleandor
To the author:
First of all, you still have the images problem (among others). Loading your home site takes around 60MB of downloads, including the autoloading 40MB MP4 file. Reduce resolution and compress. You don't need a phone to reproduce that, you just need to open your web browser development tools and reload the site to see how heavy is it. Also, the memory use calculation is off, but that's not important because probably an LLM did it.
Second, your API in karibukit.com is down
Don't rely that much in the LLM. Check things with your own eyes.
- OG_BME
Completely AI written unfortunately