Comments on: Connection Pooling: PgBouncer or JDBC http://blog.gtuhl.com/2009/04/04/connection-pooling-pgbouncer-or-jdbc/ Development, IT, Gadgets, and Startups Thu, 26 Aug 2010 15:12:11 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Joe http://blog.gtuhl.com/2009/04/04/connection-pooling-pgbouncer-or-jdbc/comment-page-1/#comment-3999 Joe Thu, 24 Sep 2009 17:17:08 +0000 http://blog.gtuhl.com/?p=276#comment-3999 We had a single pgBouncer service running on the database server. So all application servers were connecting to the same pgBouncer instance. It sounds like you have a single pgBouncer running on its own server and that sounds good/better to me - we only ran pgBouncer on the same server as the database because we didn't have another server handy. Thanks for the comment, realize I wasn't very clear above after re-reading it. In a situation where a pgBouncer service is running on each application server it seems that would create distinct pools and you would lose the advantage of a single common pool in front of the database. We had a single pgBouncer service running on the database server. So all application servers were connecting to the same pgBouncer instance. It sounds like you have a single pgBouncer running on its own server and that sounds good/better to me – we only ran pgBouncer on the same server as the database because we didn’t have another server handy.

Thanks for the comment, realize I wasn’t very clear above after re-reading it.

In a situation where a pgBouncer service is running on each application server it seems that would create distinct pools and you would lose the advantage of a single common pool in front of the database.

]]> By: digicon http://blog.gtuhl.com/2009/04/04/connection-pooling-pgbouncer-or-jdbc/comment-page-1/#comment-3998 digicon Thu, 24 Sep 2009 17:12:18 +0000 http://blog.gtuhl.com/?p=276#comment-3998 If I read your setup correctly, do you mean to say that you had pgBouncer on each application server? We have our main db server accessed only through pgBouncer which is load balanced on its own server and all applications connect through the pgBouncer server. Are there disadvantages to doing it this way? web application servers --> pgBouncer server --> db server VS. web application servers + pgBouncer service --> db server If I read your setup correctly, do you mean to say that you had pgBouncer on each application server? We have our main db server accessed only through pgBouncer which is load balanced on its own server and all applications connect through the pgBouncer server. Are there disadvantages to doing it this way?

web application servers –> pgBouncer server –> db server
VS.
web application servers + pgBouncer service –> db server

]]>