Friday
Oct182019
PostgreSQL Connection Pooling: Part 1 – Pros & Cons
Friday, October 18, 2019 at 8:51AM A long time ago, in a galaxy far far away, ‘threads’ were a programming novelty rarely used and seldom trusted. In that environment, the first PostgreSQL developers decided forking a process for each connection to the database is the safest choice. It would be a shame if your database crashed, after all.
Since then, a lot of water has flown under that bridge, but the PostgreSQL community has stuck by their original decision. It is difficult to fault their argument – as it’s absolutely true that:
tagged
Connection Pool,
Connection Pooler,
Connection Pooling,
Forking,
Language Library,
Multithreaded,
Postgres,
Web Applications,
database,
developer,
postgresql,
sql in
Database,
DevOps,
Latency,
Linux,
Performance,
Postgres,
administrator,
application,
architecture,
cluster,
connection-pool,
database performance online website,
deployment,
failure,
multilanguage,
multithreading,
open source,
postgresql,
sql Tweet
Connection Pool,
Connection Pooler,
Connection Pooling,
Forking,
Language Library,
Multithreaded,
Postgres,
Web Applications,
database,
developer,
postgresql,
sql in
Database,
DevOps,
Latency,
Linux,
Performance,
Postgres,
administrator,
application,
architecture,
cluster,
connection-pool,
database performance online website,
deployment,
failure,
multilanguage,
multithreading,
open source,
postgresql,
sql Tweet 
