zlacker

>>davidg+(OP)
Can’t believe they needed this investigation to realize they need a connection pooler. It’s a fundamental component of every large-scale Postgres deployment, especially for serverless environments.

>>paulkr+Nj2
can't believe postgres still uses a process-per-connection model that leads to endless problems like this one.

>>jstron+tl2
You can't process significantly many more queries than you've got CPU cores at the same time anyway.

>>IsTom+wL2
I disagree. If that was the case, pgBouncer wouldn't need to exist.

The problem of resource usage for many connections is real.