ST
Shaun Thomas

Shaun Thomas

Things Shaun Says on Podcasts

A Postgres architect with about twenty years of experience running and tuning production databases. He talks about connection handling and memory settings, the daily concerns of anyone operating Postgres at scale. He currently works as a Postgres architect at pgEdge and writes for Planet PostgreSQL. He has been a guest on Postgres FM, a podcast about practical Postgres operations.

Where to Find Them

Shaun Thomas has been a guest on Postgres FM .

Recently: “Estimating work_mem” on Postgres FM (August 2026).

What They Said

“My opinion there is you should never connect directly to Postgres.” — Shaun Thomas, Postgres FM

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.

Postgres FM · 2026-08-21 Permalink → Listen →
Postgres FM Around 05:17 into the episode
Shaun Thomas

No, I don't. What will RDS do? Max

Nikolay Samokhvalov

…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.

Shaun Thomas

Yeah, you could have a whole other conversation on pooling. My opinion there is you should never connect directly to Postgres.

Nikolay Samokhvalov

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.

Shaun Thomas

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.

Nikolay Samokhvalov

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…

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.

Collections They Appear In