Check for *db-pool-max-free-connections* being nil, if so don't enforce a max.
authorNathan Bird <nathan@acceleration.net>
Wed, 3 Mar 2010 19:46:22 +0000 (14:46 -0500)
committerNathan Bird <nathan@acceleration.net>
Wed, 3 Mar 2010 19:46:22 +0000 (14:46 -0500)
sql/pool.lisp

index 38d32cdd21a125c543bcbd4471b087c7cd4ffd3b..66cbaf76125d10b2a0ee600ae8044148635d3a44 100644 (file)
@@ -85,8 +85,9 @@ chance to do cleanup."
       ;;not the list). Multiple threads getting to this test at the
       ;;same time might result in the free-connections getting
       ;;longer... meh.
-      ((>= (length (free-connections pool))
-          *db-pool-max-free-connections*)
+      ((and *db-pool-max-free-connections*
+           (>= (length (free-connections pool))
+               *db-pool-max-free-connections*))
        (%pool-force-disconnect database)
        (with-process-lock ((conn-pool-lock pool) "Remove extra Conn")
         (setf (all-connections pool)