> Ok. So if all clients are busy and keep on sending transactions,
> pgbouncer cannot lower down the number of connections to PostgreSQL,
> right?
Correct. It's really a benefit for cases where each connection spends
most of its time idle (which is a very common case).
> Ok. Also I guess in Transaction mode extended protocol cannot be used
> (i.e. Java cannot be used).
Yeah, there's special issues around using JDBC and pgbouncer; in
general, using J2EE pooling is a better idea.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
_______________________________________________
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general
