Fixed #31090 -- Logged transaction management queries.

Thanks to Petter Strandmark for the original idea and Mariusz Felisiak
for advice during the DjangoConUS 2022 Sprint!

2 files changed, 9 insertions, 4 deletions

diff --git a/docs/ref/logging.txt b/docs/ref/logging.txt
index ba443a0a36..edd9f21ecb 100644
--- a/docs/ref/logging.txt
+++ b/docs/ref/logging.txt
@@ -196,9 +196,13 @@ For performance reasons, SQL logging is only enabled when
 level or handlers that are installed.
 
 This logging does not include framework-level initialization (e.g.
-``SET TIMEZONE``) or transaction management queries (e.g. ``BEGIN``,
-``COMMIT``, and ``ROLLBACK``). Turn on query logging in your database if you
-wish to view all database queries.
+``SET TIMEZONE``). Turn on query logging in your database if you wish to view
+all database queries.
+
+.. versionchanged:: 4.2
+
+    Support for logging transaction management queries (``BEGIN``, ``COMMIT``,
+    and ``ROLLBACK``) was added.
 
 .. _django-security-logger:
 
diff --git a/docs/releases/4.2.txt b/docs/releases/4.2.txt
index 8ab9242f97..e7d2882edb 100644
--- a/docs/releases/4.2.txt
+++ b/docs/releases/4.2.txt
@@ -199,7 +199,8 @@ Internationalization
 Logging
 ~~~~~~~
 
-* ...
+* The :ref:`django-db-logger` logger now logs transaction management queries
+  (``BEGIN``, ``COMMIT``, and ``ROLLBACK``) at the ``DEBUG`` level.
 
 Management Commands
 ~~~~~~~~~~~~~~~~~~~