Fixed #33717 -- Dropped support for PostgreSQL 11.

7 files changed, 15 insertions, 14 deletions

diff --git a/docs/ref/contrib/gis/install/index.txt b/docs/ref/contrib/gis/install/index.txt
index 7f4f100bb8..2277b7c5ee 100644
--- a/docs/ref/contrib/gis/install/index.txt
+++ b/docs/ref/contrib/gis/install/index.txt
@@ -58,7 +58,7 @@ supported versions, and any notes for each of the supported database backends:
 ==================  ==============================  ==================  =========================================
 Database            Library Requirements            Supported Versions  Notes
 ==================  ==============================  ==================  =========================================
-PostgreSQL          GEOS, GDAL, PROJ, PostGIS       11+                 Requires PostGIS.
+PostgreSQL          GEOS, GDAL, PROJ, PostGIS       12+                 Requires PostGIS.
 MySQL               GEOS, GDAL                      5.7+                :ref:`Limited functionality <mysql-spatial-limitations>`.
 Oracle              GEOS, GDAL                      19+                 XE not supported.
 SQLite              GEOS, GDAL, PROJ, SpatiaLite    3.9.0+              Requires SpatiaLite 4.3+
diff --git a/docs/ref/contrib/postgres/constraints.txt b/docs/ref/contrib/postgres/constraints.txt
index 26c6356693..44f1f56db1 100644
--- a/docs/ref/contrib/postgres/constraints.txt
+++ b/docs/ref/contrib/postgres/constraints.txt
@@ -139,8 +139,8 @@ used for queries that select only included fields
 (:attr:`~ExclusionConstraint.include`) and filter only by indexed fields
 (:attr:`~ExclusionConstraint.expressions`).
 
-``include`` is supported for GiST indexes on PostgreSQL 12+ and SP-GiST
-indexes on PostgreSQL 14+.
+``include`` is supported for GiST indexes. PostgreSQL 14+ also supports
+``include`` for SP-GiST indexes.
 
 .. versionchanged:: 4.1
 
diff --git a/docs/ref/contrib/postgres/fields.txt b/docs/ref/contrib/postgres/fields.txt
index fe4b3856ab..d460cecc70 100644
--- a/docs/ref/contrib/postgres/fields.txt
+++ b/docs/ref/contrib/postgres/fields.txt
@@ -287,8 +287,8 @@ transform do not change. For example::
 
 .. admonition:: Case-insensitive collations
 
-    On PostgreSQL 12+, it's preferable to use non-deterministic collations
-    instead of the ``citext`` extension. You can create them using the
+    It's preferable to use non-deterministic collations instead of the
+    ``citext`` extension. You can create them using the
     :class:`~django.contrib.postgres.operations.CreateCollation` migration
     operation. For more details, see :ref:`manage-postgresql-collations` and
     the PostgreSQL documentation about `non-deterministic collations`_.
diff --git a/docs/ref/contrib/postgres/operations.txt b/docs/ref/contrib/postgres/operations.txt
index 46ba3300ae..d5b8a9e0d6 100644
--- a/docs/ref/contrib/postgres/operations.txt
+++ b/docs/ref/contrib/postgres/operations.txt
@@ -151,10 +151,6 @@ For example, to create a collation for German phone book ordering::
     ``provider``, and ``deterministic`` arguments. Therefore, ``locale`` is
     required to make this operation reversible.
 
-.. admonition:: Restrictions
-
-    Non-deterministic collations are supported only on PostgreSQL 12+.
-
 Concurrent index operations
 ===========================
 
diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt
index a80c10e8f6..9c6c241184 100644
--- a/docs/ref/databases.txt
+++ b/docs/ref/databases.txt
@@ -114,7 +114,7 @@ below for information on how to set up your database correctly.
 PostgreSQL notes
 ================
 
-Django supports PostgreSQL 11 and higher. `psycopg2`_ 2.8.4 or higher is
+Django supports PostgreSQL 12 and higher. `psycopg2`_ 2.8.4 or higher is
 required, though the latest release is recommended.
 
 .. _psycopg2: https://www.psycopg.org/
diff --git a/docs/ref/models/indexes.txt b/docs/ref/models/indexes.txt
index 6b3c7422b7..c6633d6998 100644
--- a/docs/ref/models/indexes.txt
+++ b/docs/ref/models/indexes.txt
@@ -214,10 +214,9 @@ See the PostgreSQL documentation for more details about `covering indexes`_.
 
 .. admonition:: Restrictions on PostgreSQL
 
-    PostgreSQL < 12 only supports covering B-Tree indexes, PostgreSQL 12+ also
-    supports covering :class:`GiST indexes
-    <django.contrib.postgres.indexes.GistIndex>`, and PostgreSQL 14+ also
-    supports covering :class:`SP-GiST indexes
+    PostgreSQL supports covering B-Tree and :class:`GiST indexes
+    <django.contrib.postgres.indexes.GistIndex>`. PostgreSQL 14+ also supports
+    covering :class:`SP-GiST indexes
     <django.contrib.postgres.indexes.SpGistIndex>`.
 
 .. versionchanged:: 4.1
diff --git a/docs/releases/4.2.txt b/docs/releases/4.2.txt
index 9c16ae870e..0d95f68654 100644
--- a/docs/releases/4.2.txt
+++ b/docs/releases/4.2.txt
@@ -229,6 +229,12 @@ Dropped support for MariaDB 10.3
 Upstream support for MariaDB 10.3 ends in May 2023. Django 4.2 supports MariaDB
 10.4 and higher.
 
+Dropped support for PostgreSQL 11
+---------------------------------
+
+Upstream support for PostgreSQL 11 ends in November 2023. Django 4.2 supports
+PostgreSQL 12 and higher.
+
 Miscellaneous
 -------------