From dbe263751cf80732c2cd47d409f5f0a9701ec327 Mon Sep 17 00:00:00 2001 From: Alberto Sottile Date: Fri, 12 May 2023 13:09:38 +0200 Subject: [PATCH] [4.2.x] Clarified database connections lifetime outside HTTP requests. Backport of e901407e2369ddb16a5c866e1f2fbf8ea8acf549 from main --- docs/ref/databases.txt | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index 3334619f91..5a26520501 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -31,7 +31,7 @@ Persistent connections ---------------------- Persistent connections avoid the overhead of reestablishing a connection to -the database in each request. They're controlled by the +the database in each HTTP request. They're controlled by the :setting:`CONN_MAX_AGE` parameter which defines the maximum lifetime of a connection. It can be set independently for each database. @@ -101,6 +101,10 @@ either restore Django's defaults at the end of each request, force an appropriate value at the beginning of each request, or disable persistent connections. +If a connection is created in a long-running process, outside of Django’s +request-response cycle, the connection will remain open until explicitly +closed, or timeout occurs. + Encoding --------