Scott Marlowe <scott.marlowe@xxxxxxxxx> wrote: > Hannu Krosing <hannu@xxxxxxxxxxxxxxx> wrote: >> One example where you need a separate connection pool is pooling >> really large number of connections, which you may want to do on >> another host than the database itself is running. > > Definitely. Often it's best placed on the individual webservers > that are making requests, each running its own pool. Each running its own pool? You've just made a case for an admissions policy based on active database transactions or active queries (or both) on the server having a benefit when used with this pooling arrangement. This collection of pools can't know when the CPUs have enough to keep them busy and adding more will degrade performance. -Kevin -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
