Removed versionadded/changed annotations for 3.2.

4 files changed, 0 insertions, 51 deletions

diff --git a/docs/ref/contrib/postgres/aggregates.txt b/docs/ref/contrib/postgres/aggregates.txt
index 9223f17ab8..cc177aca87 100644
--- a/docs/ref/contrib/postgres/aggregates.txt
+++ b/docs/ref/contrib/postgres/aggregates.txt
@@ -130,15 +130,11 @@ General-purpose aggregation functions
 
     .. attribute:: distinct
 
-        .. versionadded:: 3.2
-
         An optional boolean argument that determines if array values will be
         distinct. Defaults to ``False``.
 
     .. attribute:: ordering
 
-        .. versionadded:: 3.2
-
         An optional string of a field name (with an optional ``"-"`` prefix
         which indicates descending order) or an expression (or a tuple or list
         of strings and/or expressions) that specifies the ordering of the
diff --git a/docs/ref/contrib/postgres/constraints.txt b/docs/ref/contrib/postgres/constraints.txt
index 7907eaefdf..cb4347dd95 100644
--- a/docs/ref/contrib/postgres/constraints.txt
+++ b/docs/ref/contrib/postgres/constraints.txt
@@ -109,8 +109,6 @@ enforced immediately after every command.
 
 .. attribute:: ExclusionConstraint.include
 
-.. versionadded:: 3.2
-
 A list or tuple of the names of the fields to be included in the covering
 exclusion constraint as non-key columns. This allows index-only scans to be
 used for queries that select only included fields
@@ -124,8 +122,6 @@ used for queries that select only included fields
 
 .. attribute:: ExclusionConstraint.opclasses
 
-.. versionadded:: 3.2
-
 The names of the `PostgreSQL operator classes
 <https://www.postgresql.org/docs/current/indexes-opclass.html>`_ to use for
 this constraint. If you require a custom operator class, you must provide one
diff --git a/docs/ref/contrib/postgres/indexes.txt b/docs/ref/contrib/postgres/indexes.txt
index 9a9b7fc73b..de1715c239 100644
--- a/docs/ref/contrib/postgres/indexes.txt
+++ b/docs/ref/contrib/postgres/indexes.txt
@@ -28,11 +28,6 @@ available from the ``django.contrib.postgres.indexes`` module.
 
     .. _bloom: https://www.postgresql.org/docs/current/bloom.html
 
-    .. versionchanged:: 3.2
-
-        Positional argument ``*expressions`` was added in order to support
-        functional indexes.
-
 ``BrinIndex``
 =============
 
@@ -46,11 +41,6 @@ available from the ``django.contrib.postgres.indexes`` module.
 
     The ``pages_per_range`` argument takes a positive integer.
 
-    .. versionchanged:: 3.2
-
-        Positional argument ``*expressions`` was added in order to support
-        functional indexes.
-
     .. _automatic summarization: https://www.postgresql.org/docs/current/brin-intro.html#BRIN-OPERATION
 
 ``BTreeIndex``
@@ -63,11 +53,6 @@ available from the ``django.contrib.postgres.indexes`` module.
     Provide an integer value from 10 to 100 to the fillfactor_ parameter to
     tune how packed the index pages will be. PostgreSQL's default is 90.
 
-    .. versionchanged:: 3.2
-
-        Positional argument ``*expressions`` was added in order to support
-        functional indexes.
-
     .. _fillfactor: https://www.postgresql.org/docs/current/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS
 
 ``GinIndex``
@@ -92,11 +77,6 @@ available from the ``django.contrib.postgres.indexes`` module.
     to tune the maximum size of the GIN pending list which is used when
     ``fastupdate`` is enabled.
 
-    .. versionchanged:: 3.2
-
-        Positional argument ``*expressions`` was added in order to support
-        functional indexes.
-
     .. _GIN Fast Update Technique: https://www.postgresql.org/docs/current/gin-implementation.html#GIN-FAST-UPDATE
     .. _gin_pending_list_limit: https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-GIN-PENDING-LIST-LIMIT
 
@@ -127,11 +107,6 @@ available from the ``django.contrib.postgres.indexes`` module.
     Provide an integer value from 10 to 100 to the fillfactor_ parameter to
     tune how packed the index pages will be. PostgreSQL's default is 90.
 
-    .. versionchanged:: 3.2
-
-        Positional argument ``*expressions`` was added in order to support
-        functional indexes.
-
     .. _buffering build: https://www.postgresql.org/docs/current/gist-implementation.html#GIST-BUFFERING-BUILD
     .. _fillfactor: https://www.postgresql.org/docs/current/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS
 
@@ -150,11 +125,6 @@ available from the ``django.contrib.postgres.indexes`` module.
         Hash indexes have been available in PostgreSQL for a long time, but
         they suffer from a number of data integrity issues in older versions.
 
-    .. versionchanged:: 3.2
-
-        Positional argument ``*expressions`` was added in order to support
-        functional indexes.
-
     .. _fillfactor: https://www.postgresql.org/docs/current/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS
 
 ``SpGistIndex``
@@ -168,18 +138,11 @@ available from the ``django.contrib.postgres.indexes`` module.
     Provide an integer value from 10 to 100 to the fillfactor_ parameter to
     tune how packed the index pages will be. PostgreSQL's default is 90.
 
-    .. versionchanged:: 3.2
-
-        Positional argument ``*expressions`` was added in order to support
-        functional indexes.
-
     .. _fillfactor: https://www.postgresql.org/docs/current/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS
 
 ``OpClass()`` expressions
 =========================
 
-.. versionadded:: 3.2
-
 .. class:: OpClass(expression, name)
 
     An ``OpClass()`` expression represents the ``expression`` with a custom
diff --git a/docs/ref/contrib/postgres/operations.txt b/docs/ref/contrib/postgres/operations.txt
index 4a0ef7a6b8..b63598cb1b 100644
--- a/docs/ref/contrib/postgres/operations.txt
+++ b/docs/ref/contrib/postgres/operations.txt
@@ -38,10 +38,6 @@ have to create the extension outside of Django migrations with a user that has
 them. In that case, connect to your Django database and run the query
 ``CREATE EXTENSION IF NOT EXISTS hstore;``.
 
-.. versionchanged:: 3.2
-
-    In older versions, the pre-existence of the extension isn't checked.
-
 .. currentmodule:: django.contrib.postgres.operations
 
 ``CreateExtension``
@@ -118,8 +114,6 @@ them. In that case, connect to your Django database and run the query
 Managing collations using migrations
 ====================================
 
-.. versionadded:: 3.2
-
 If you need to filter or order a column using a particular collation that your
 operating system provides but PostgreSQL does not, you can manage collations in
 your database using a migration file. These collations can then be used with