←back to thread

366 points virtualwhys | 3 comments | | HN request time: 0.633s | source
1. vinnymac ◴[] No.41897492[source]
The part I hate the most is that in 2024 I still need a connection pooler (such as pgbouncer) in front of it to make it usable.
replies(1): >>41901827 #
2. bvrmn ◴[] No.41901827[source]
Let me guess, PHP?
replies(1): >>41903625 #
3. nobleach ◴[] No.41903625[source]
I see this pattern all over the place, not just PHP. When leveraging containers, what's a better option? Certainly Java, Rust, even NodeJS all have decent enough connection pools for PG. But telling those apps that are running in those containers, "uhhh, you're just one among many so, your pooling strategy may not represent reality". I've seen folks try to solve this by literally doing replica math when an app boots up (are there 8 replicas running? ok, divide Postgres' default 100 connections by that). Moving the pool outside the app container seems like a better move.