fix: document proper pool timeout behaviour #DA-919 (#6141)

* fix: document proper pool timeout behaviour * Update content/300-accelerate/250-connection-pooling.mdx Co-authored-by: Jon Harrell <[email protected]> * Update content/300-accelerate/250-connection-pooling.mdx Co-authored-by: Tyler Benfield <[email protected]> --------- Co-authored-by: Jon Harrell <[email protected]> Co-authored-by: Tyler Benfield <[email protected]>
prisma · Jul 8, 2024 · 963ef69 · 963ef69
1 parent 93b8273
commit 963ef69
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/content/300-accelerate/250-connection-pooling.mdx b/content/300-accelerate/250-connection-pooling.mdx
@@ -40,7 +40,7 @@ To change the size of the connection pool:
 
 ### Configuring the connection pool timeout
 
-The connection pool timeout is the duration, measured in seconds, during which the query engine must process a specific query; failing to do so within this time frame results in an exception being thrown, and the system proceeds to the next query in the queue.
+The connection pool timeout is the maximum number of seconds that a query will block while waiting for a connection from Accelerate's internal connection pool. This occurs if the number of concurrent requests exceeds the connection limit, resulting in queueing of additional requests until a free connection becomes available. An exception is thrown if a free connection does not become available within the pool timeout. The connection pool timeout can be disabled by setting the value to 0.
 
 Similar to the connection pool size, you may also configure the connection pool timeout via the _database connection string_. To adjust this value, you may add the `pool_timeout` parameter to the database connection string.