Doc: remove notes about the version vacuumdb options are valid from

Here we remove the notes which mention which version the given vacuumdb
option is available from.  There are now 11 of these notes and they're
both quite untidy and take up far more space than they seem to be worth.
On running a print preview of the compiled HTML, removing these notes
saves about 1 A4 page (~20% less space).

If people need to see which options are available on older versions, then
consulting the documents for that version seems like a good idea.  In any
case, when using newer vacuumdb versions on older servers, the user will
receive an error if they try to use an unsupported option.

Additionally, 3 of the notes are warning about the option only being
available from PostgreSQL 9.6 and later.  That version's support ended 2.5
years ago.  So, it's quite clear that the value of these notes diminishes
over time.

Discussion: https://postgr.es/m/CAApHDvrCQn6tupx2R67VL9RP1Qy4dDuWKRvt4jaB0vk2akQchw@mail.gmail.com

1 files changed, 0 insertions, 66 deletions

diff --git a/doc/src/sgml/ref/vacuumdb.sgml b/doc/src/sgml/ref/vacuumdb.sgml
index 35600ec749..da2393783b 100644
--- a/doc/src/sgml/ref/vacuumdb.sgml
+++ b/doc/src/sgml/ref/vacuumdb.sgml
@@ -131,12 +131,6 @@ PostgreSQL documentation
         This size is used to calculate the number of shared buffers which will
         be reused as part of this strategy.  See <xref linkend="sql-vacuum"/>.
        </para>
-       <note>
-        <para>
-         This option is only available for servers running
-         <productname>PostgreSQL</productname> 16 and later.
-        </para>
-       </note>
       </listitem>
      </varlistentry>
 
@@ -164,12 +158,6 @@ PostgreSQL documentation
        <para>
         Disable skipping pages based on the contents of the visibility map.
        </para>
-       <note>
-        <para>
-         This option is only available for servers running
-         <productname>PostgreSQL</productname> 9.6 and later.
-        </para>
-       </note>
       </listitem>
      </varlistentry>
 
@@ -210,12 +198,6 @@ PostgreSQL documentation
        <para>
         Always remove index entries pointing to dead tuples.
        </para>
-       <note>
-        <para>
-         This option is only available for servers running
-         <productname>PostgreSQL</productname> 12 and later.
-        </para>
-       </note>
       </listitem>
      </varlistentry>
 
@@ -261,12 +243,6 @@ PostgreSQL documentation
         <acronym>TOAST</acronym> table for the relation if necessary, it does
         not need to be considered separately.
        </para>
-       <note>
-        <para>
-         This option is only available for servers running
-         <productname>PostgreSQL</productname> 9.6 and later.
-        </para>
-       </note>
       </listitem>
      </varlistentry>
 
@@ -288,12 +264,6 @@ PostgreSQL documentation
         <acronym>TOAST</acronym> table for the relation if necessary, it does
         not need to be considered separately.
        </para>
-       <note>
-        <para>
-         This option is only available for servers running
-         <productname>PostgreSQL</productname> 9.6 and later.
-        </para>
-       </note>
       </listitem>
      </varlistentry>
 
@@ -327,12 +297,6 @@ PostgreSQL documentation
        <para>
         Do not remove index entries pointing to dead tuples.
        </para>
-       <note>
-        <para>
-         This option is only available for servers running
-         <productname>PostgreSQL</productname> 12 and later.
-        </para>
-       </note>
       </listitem>
      </varlistentry>
 
@@ -342,12 +306,6 @@ PostgreSQL documentation
        <para>
         Skip the main relation.
        </para>
-       <note>
-        <para>
-         This option is only available for servers running
-         <productname>PostgreSQL</productname> 16 and later.
-        </para>
-       </note>
       </listitem>
      </varlistentry>
 
@@ -357,12 +315,6 @@ PostgreSQL documentation
        <para>
         Skip the TOAST table associated with the table to vacuum, if any.
        </para>
-       <note>
-        <para>
-         This option is only available for servers running
-         <productname>PostgreSQL</productname> 14 and later.
-        </para>
-       </note>
       </listitem>
      </varlistentry>
 
@@ -372,12 +324,6 @@ PostgreSQL documentation
        <para>
         Do not truncate empty pages at the end of the table.
        </para>
-       <note>
-        <para>
-         This option is only available for servers running
-         <productname>PostgreSQL</productname> 12 and later.
-        </para>
-       </note>
       </listitem>
      </varlistentry>
 
@@ -390,12 +336,6 @@ PostgreSQL documentation
         This allows the vacuum to leverage multiple CPUs to process indexes.
         See <xref linkend="sql-vacuum"/>.
        </para>
-       <note>
-        <para>
-         This option is only available for servers running
-         <productname>PostgreSQL</productname> 13 and later.
-        </para>
-       </note>
       </listitem>
      </varlistentry>
 
@@ -415,12 +355,6 @@ PostgreSQL documentation
        <para>
         Skip relations that cannot be immediately locked for processing.
        </para>
-       <note>
-        <para>
-         This option is only available for servers running
-         <productname>PostgreSQL</productname> 12 and later.
-        </para>
-       </note>
       </listitem>
      </varlistentry>