Fixed #36623 -- Dropped support for PostgreSQL 14 and PostGIS 3.1.

docs/ref/contrib/gis/install/geolibs.txt

@@ -17,7 +17,7 @@ Program                         Description                           Required
 `PROJ`_                         Cartographic Projections library      Yes (PostgreSQL and SQLite only)  9.x, 8.x, 7.x, 6.x
 :ref:`GDAL <gdal-overview>`     Geospatial Data Abstraction Library   Yes                               3.11, 3.10, 3.9, 3.8, 3.7, 3.6, 3.5, 3.4, 3.3, 3.2, 3.1
 :ref:`GeoIP <geoip2-overview>`  IP-based geolocation library          No                                2
-`PostGIS`__                     Spatial extensions for PostgreSQL     Yes (PostgreSQL only)             3.5, 3.4, 3.3, 3.2, 3.1
+`PostGIS`__                     Spatial extensions for PostgreSQL     Yes (PostgreSQL only)             3.5, 3.4, 3.3, 3.2
 `SpatiaLite`__                  Spatial extensions for SQLite         Yes (SQLite only)                 5.1, 5.0, 4.3
 ==============================  ====================================  ================================  =======================================================
 
@@ -44,7 +44,6 @@ totally fine with GeoDjango. Your mileage may vary.
     GDAL 3.9.0 2024-05-10
     GDAL 3.10.0 2024-11-06
     GDAL 3.11.0 2025-05-09
-    PostGIS 3.1.0 2020-12-18
     PostGIS 3.2.0 2021-12-18
     PostGIS 3.3.0 2022-08-27
     PostGIS 3.4.0 2023-08-15

docs/ref/contrib/gis/install/index.txt

@@ -57,7 +57,7 @@ supported versions, and any notes for each of the supported database backends:
 ==================  ==============================  ==================  =========================================
 Database            Library Requirements            Supported Versions  Notes
 ==================  ==============================  ==================  =========================================
-PostgreSQL          GEOS, GDAL, PROJ, PostGIS       14+                 Requires PostGIS.
+PostgreSQL          GEOS, GDAL, PROJ, PostGIS       15+                 Requires PostGIS.
 MySQL               GEOS, GDAL                      8.0.11+             :ref:`Limited functionality <mysql-spatial-limitations>`.
 Oracle              GEOS, GDAL                      19+                 XE not supported.
 SQLite              GEOS, GDAL, PROJ, SpatiaLite    3.31.0+             Requires SpatiaLite 4.3+
@@ -305,7 +305,7 @@ Summary:
 
 .. code-block:: shell
 
-    $ sudo port install postgresql14-server
+    $ sudo port install postgresql15-server
     $ sudo port install geos
     $ sudo port install proj6
     $ sudo port install postgis3
@@ -319,14 +319,14 @@ Summary:
 
     .. code-block:: shell
 
-        export PATH=/opt/local/bin:/opt/local/lib/postgresql14/bin
+        export PATH=/opt/local/bin:/opt/local/lib/postgresql15/bin
 
     In addition, add the ``DYLD_FALLBACK_LIBRARY_PATH`` setting so that
     the libraries can be found by Python:
 
     .. code-block:: shell
 
-        export DYLD_FALLBACK_LIBRARY_PATH=/opt/local/lib:/opt/local/lib/postgresql14
+        export DYLD_FALLBACK_LIBRARY_PATH=/opt/local/lib:/opt/local/lib/postgresql15
 
 __ https://www.macports.org/
 

docs/ref/contrib/postgres/aggregates.txt

@@ -76,7 +76,7 @@ General-purpose aggregation functions
 .. class:: BitXor(expression, filter=None, default=None, **extra)
 
     Returns an ``int`` of the bitwise ``XOR`` of all non-null input values, or
-    ``default`` if all values are null. It requires PostgreSQL 14+.
+    ``default`` if all values are null.
 
 ``BoolAnd``
 -----------

docs/ref/contrib/postgres/constraints.txt

@@ -130,8 +130,7 @@ 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. PostgreSQL 14+ also supports
-``include`` for SP-GiST indexes.
+``include`` is supported for GiST and SP-GiST indexes.
 
 ``violation_error_code``
 ------------------------

docs/ref/databases.txt

@@ -119,7 +119,7 @@ below for information on how to set up your database correctly.
 PostgreSQL notes
 ================
 
-Django supports PostgreSQL 14 and higher. `psycopg`_ 3.1.12+ or `psycopg2`_
+Django supports PostgreSQL 15 and higher. `psycopg`_ 3.1.12+ or `psycopg2`_
 2.9.9+ is required, though the latest `psycopg`_ 3.1.12+ is recommended.
 
 .. note::

docs/ref/models/constraints.txt

@@ -273,7 +273,7 @@ creates a unique constraint that only allows one row to store a ``NULL`` value
 in the ``ordering`` column.
 
 Unique constraints with ``nulls_distinct`` are ignored for databases besides
-PostgreSQL 15+.
+PostgreSQL.
 
 ``violation_error_code``
 ------------------------

docs/ref/models/indexes.txt

@@ -214,9 +214,8 @@ See the PostgreSQL documentation for more details about `covering indexes`_.
 
 .. admonition:: Restrictions on PostgreSQL
 
-    PostgreSQL supports covering B-Tree and :class:`GiST indexes
-    <django.contrib.postgres.indexes.GistIndex>`. PostgreSQL 14+ also supports
-    covering :class:`SP-GiST indexes
+    PostgreSQL supports covering B-Tree, :class:`GiST indexes
+    <django.contrib.postgres.indexes.GistIndex>`, and :class:`SP-GiST indexes
     <django.contrib.postgres.indexes.SpGistIndex>`.
 
 .. _covering indexes: https://www.postgresql.org/docs/current/indexes-index-only-scans.html

docs/releases/6.1.txt

@@ -248,6 +248,17 @@ backends.
   database has native support for ``DurationField``, override this method to
   simply return the value.
 
+:mod:`django.contrib.gis`
+-------------------------
+
+* Support for PostGIS 3.1 is removed.
+
+Dropped support for PostgreSQL 14
+---------------------------------
+
+Upstream support for PostgreSQL 14 ends in November 2026. Django 6.1 supports
+PostgreSQL 15 and higher.
+
 Miscellaneous
 -------------