On Thu, Jul 8, 2010 at 11:48 PM, 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. -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
