Matthew Wakeling wrote:
> If you have an external pool solution, you can put it somewhere else -
> maybe on multiple somewhere elses.
This is the key point to observe: if you're at the point where you have
so many connections that you need a pool, the last place you want to put
that is on the overloaded database server itself. Therefore, it must be
an external piece of software to be effective, rather than being part of
the server itself. Database servers are relatively expensive computing
hardware due to size/quantity/quality of disks required. You can throw
a pooler (or poolers) on any cheap 1U server. This is why a built-in
pooler, while interesting, is not particularly functional for how people
normally scale up real-world deployments.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com www.2ndQuadrant.us
