From 06f8ade4128c181776b8018fc73b0b9e1f383a25 Mon Sep 17 00:00:00 2001
From: Nathan Bird <nathan@acceleration.net>
Date: Wed, 3 Mar 2010 14:46:22 -0500
Subject: [PATCH] Check for *db-pool-max-free-connections* being nil, if so
 don't enforce a max.

---
 sql/pool.lisp | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/sql/pool.lisp b/sql/pool.lisp
index 38d32cd..66cbaf7 100644
--- a/sql/pool.lisp
+++ b/sql/pool.lisp
@@ -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)
-- 
2.34.1