Just as a follow up, we are using pgpool for replication, not connection
pooling.
Client application is mixture of Microsoft Visual FoxPro 9 (via odbc)
and java GWT-based applications. Some of VFP applications run as
scheduled jobs so start, connect via pgpool, run the queires/updates,
disconnect and exit and I can see the connections appearing/disappearing
on the database (pgAdmin 1.8.4 again via pgpool).
With connection caching enabled, the number of connections opened by VFP
routines did not close when the application exited so the concurrent
connections kept growing until the server reached its maximum number of
connections. Setting connection caching false cured this problem.
No virus found in this outgoing message.
Checked by AVG - www.avg.com
Version: 8.5.281 / Virus Database: 270.11.28/2022 - Release Date: 03/25/09
07:16:00
_______________________________________________
Pgpool-general mailing list
[email protected]
http://pgfoundry.org/mailman/listinfo/pgpool-general
