i've run into problems with apache/php/mysql where mysqld's max_connections is less than the number of httpd processes are running, because php's pconnect will create a persistent connection per process.
my understanding of the pg library you are using is it will setup a number of connections up front and then use them in parallel to service the cursors your app opens. i don't think you will run into the same problem as long as you are using a connection pool. On Thu, 24 Feb 2005 14:10:20 -0700, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I've thought if that as well. I am pretty new to using postgres as my > main database, most of my experience has been with mysql, and at least > with mysql I would run into problems if I didn't explicitly close the > connection, leaving it open would eventually crash the server. So I > guess what I need to know, is this less of an issue with postgres? > Jose ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
