The episode is about estimating work_mem, and it detours into connection limits: Nikolay Samokhvalov notes that RDS defaults to thousands of max connections and that plenty of customers run with no pooler at all. Thomas answers with a flat rule rather than a tuning tip. He goes straight back to sampling active connections afterwards.
No, I don't. What will RDS do? Max
…but we observe a lot of customers who come to us, they don't. No pitcher bouncer, no RDS proxy, only some poolers are on application side. And those guys who run application nodes, they put it to Kubernetes with auto-scaling. So nobody knows which probability of reaching those 5,000 connections.
Yeah, you could have a whole other conversation on pooling. My opinion there is you should never connect directly to Postgres.
Right. Well, yeah, pooler should be inside. Yeah, I agree. But this is the reality. And RDS is the most popular one. And people come with 16 V CPUs, 25 or 50 hundred Max connections.
Yeah. At that point, you get to an area where you have to say sample your number of active connections and then it's a little more involved, but it's roughly the same idea.
Yeah, so this is great. And this is like for many years it was my number one approach. Basically, we tune based on observations. Feedback loop, right? But I really want something more like not looking into actual thing, but predicting something, right? Because sometimes you launch new service or…