7 ms·

You'd be surprised how websites are out there running Wordpress/phpBB and managing 100+ concurrent connections with per-process pooling.

• castorp 5y ago
  "hundreds" of concurrent connections isn't really a problem for Postgres. Several thousands are - at least up until now. V14 will improve this substantially.
  • tomnipotent 5y ago
    Plenty of people are running on VPS or other shared hosting, with generally limited resources.
    • pgaddict 5y ago
      Well, I'd argue that's more an issue of the web application. If you're on a system with limited resources, and the webapp insists on opening hundreds of connections, assuming they're free of charge, it's a bit silly. Anyway, this is unlikely to change anytime soon, given the Postgres connection/process model. We're continuously improving things, but each connection has some non-negligible costs (CPU, memory), so in those cases a connection pool is still a good idea.