Postgres definitely does not exhibit this behavior. Since I inherited a
lot of databases I have a fair mix of both MySQL and Postgres. I
struggled for a long time with MySQL lost connection problems hanging
the app server, however once I switched all the MySQL operations to use
built on demand connections the problems have disappeared completely.
For the Postgres DBs I still use connection sharing leaving an odd mix
of both.
FWIW, my understanding is that MySQL connections are quick to make and you don't gain much from pooling (at least if the server is on the same host as the client). So it might not be so bad to avoid pooling connections entirely. I know this isn't true for a lot of other databases, and I don't know much time Postgres connections take, but maybe other people have run their own experiments (e.g., running a thousand simple queries, once with a single connection and another time with new connections for each query).
-- Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org
------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
