On Thu, Aug 26, 2010 at 23:13, Scott Marlowe <scott.marlowe@xxxxxxxxx> wrote: > On Thu, Aug 26, 2010 at 2:29 PM, Maria L. Wilson > <Maria.L.Wilson-1@xxxxxxxx> wrote: >> >> >> we have this application (using jboss/java/hibernate) on linux accessing >> data on 3 postgres database servers using 8.4.1. >> >> One of our many concerns has been the way we handle connections to the >> database. java/hibernate handle their own pooling so I understand that >> using anything else is out of the question. > > It's not impossible to put another connection pooler between hibernate > and your database server. May not be useful or better, but it's > possible. I've been using pgbouncer in combination with the jboss connection pooler several times, mainly for the reason that reconfiguring the jboss connection poolers (particularly if you have lots of them) can cause quite a bit of downtime. Just sticking a 1-1 mapping pgbouncer in between with support for SUSPEND makes a lot of difference if you switch master/slave on your replication /ha. It'll still break the connections for jboss, but it'll recover from that a *lot* faster than a reconfig. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
