Prisma's pgbouncer=true on Supabase made every query 4 round-trips (postmortem) • Hacker News Board

Re: Prisma's pgbouncer=true on Supabase made every query 4 round-trips (postmortem)

#11

Post by tecleandor » Wed, Sep 16, 2026, 6:02 PM UTC

Tostino wrote: post #7

ProjectBarks wrote: post #6

> "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?

That's how postmortems have been written for ages.

It'd be great if it were written as a postmortem, but seems like that's almost the only moment where a concrete hour is mentioned. Except for the screenshot footnote.

Re: Prisma's pgbouncer=true on Supabase made every query 4 round-trips (postmortem)

#12

Post by smallnix » Wed, Sep 16, 2026, 6:12 PM UTC

> The crash and the slowness turned out to be unrelated. The crash is the short story; the slowness is the one worth writing down.

And that's not slop, it's the real smoking load bearing foot gun.

Re: Prisma's pgbouncer=true on Supabase made every query 4 round-trips (postmortem)

#13

Post by wmadden » Wed, Sep 16, 2026, 6:16 PM UTC

tonymillion wrote: post #8

I tried to read this article but something about the writing style made me go cross eyed. That being said, it sounded like something I had heard before and lo and behold... Literally raised 4 years ago: https://github.com/prisma/orm/discussions/15164 I'm not sure the real intention of this blogpost, but my takeaway is "someone who has no idea what is going on finds a problem left for them, like a little code land min…

I mean, the real takeaway is they’re using Prisma 5. That reached EOL years ago, we’re on Prisma 8 now

Re: Prisma's pgbouncer=true on Supabase made every query 4 round-trips (postmortem)

#14

Post by tecleandor » Wed, Sep 16, 2026, 6:27 PM UTC

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.