[1.7.x] Fixed #22417 -- Added additional documentation for refs #16969.

Thanks Jon Foster for the report.

Backport of 1b3a3fc1e4 from master

2 files changed, 9 insertions, 0 deletions

diff --git a/docs/releases/1.7.txt b/docs/releases/1.7.txt
index 52edbb4a58..d0fe0a5620 100644
--- a/docs/releases/1.7.txt
+++ b/docs/releases/1.7.txt
@@ -1247,6 +1247,10 @@ Miscellaneous
   The :attr:`~django.core.validators.RegexValidator.flags` attribute was added
   to :class:`~django.core.validators.RegexValidator` to simplify this change.
 
+* When running tests on PostgreSQL, the :setting:`USER` will need read access
+  to the built-in ``postgres`` database. This is in lieu of the previous
+  behavior of connecting to the actual non-test database.
+
 .. _deprecated-features-1.7:
 
 Features deprecated in 1.7
diff --git a/docs/topics/testing/overview.txt b/docs/topics/testing/overview.txt
index 4c7e67c4b1..db7c074a4f 100644
--- a/docs/topics/testing/overview.txt
+++ b/docs/topics/testing/overview.txt
@@ -173,6 +173,11 @@ entirely!). If you want to use a different database name, specify
 :setting:`NAME <TEST_NAME>` in the :setting:`TEST <DATABASE-TEST>`
 dictionary for any given database in :setting:`DATABASES`.
 
+.. versionchanged:: 1.7
+
+    On PostgreSQL, :setting:`USER` will also need read access to the built-in
+    ``postgres`` database.
+
 Aside from using a separate database, the test runner will otherwise
 use all of the same database settings you have in your settings file:
 :setting:`ENGINE <DATABASE-ENGINE>`, :setting:`USER`, :setting:`HOST`, etc. The