Browse Teach Curate

Connection Pooling

Database connections are expensive to open and each consumes server memory and a backend process/thread, so a pool keeps a fixed set of warm connections that clients borrow and return. The pool size caps useful concurrency; sizing it near the server's core and IO capacity outperforms thousands of direct connections.

Questions this Concept answers

Why is opening a PostgreSQL connection expensive enough to pool?

jeremy Video

Why PostgreSQL Needs a Connection Pool: One Operating System Process Per Connection

PostgreSQL uses a process-per-connection model: a supervising backend accepts each incoming connection and forks a dedicated operating system process for it, which is destroyed when the connection cl…