doc: Specify when ssl_prefer_server_ciphers was added
authorDaniel Gustafsson <[email protected]>
Thu, 4 Jul 2024 09:38:37 +0000 (11:38 +0200)
committerDaniel Gustafsson <[email protected]>
Thu, 4 Jul 2024 09:38:37 +0000 (11:38 +0200)
The ssl_prefer_server_ciphers setting is quite important from a
security point of view, so simply stating that older versions
doesn't have it isn't very helpful.  This adds the version when
the GUC was added to help readers.

Backpatch to all supported versions since this setting has been
around since 9.4.

Reviewed-by: Peter Eisentraut <[email protected]>
Reviewed-by: Tom Lane <[email protected]>
Discussion: https://postgr.es/m/5D7E0F5E-E620-4D54-8788-66D421AC76F0@yesql.se
Backpatch-through: v12

doc/src/sgml/config.sgml

index 3c95e54053dade0397849336d45f7f4b7838352c..1c7e9eadbb14ca698d5a614c5bdec8262f6cf238 100644 (file)
@@ -1326,11 +1326,11 @@ include_dir 'conf.d'
        </para>
 
        <para>
-        Older PostgreSQL versions do not have this setting and always use the
-        client's preferences.  This setting is mainly for backward
-        compatibility with those versions.  Using the server's preferences is
-        usually better because it is more likely that the server is appropriately
-        configured.
+        <productname>PostgreSQL</productname> versions before 9.4 do not have
+        this setting and always use the client's preferences.  This setting is
+        mainly for backward compatibility with those versions.  Using the
+        server's preferences is usually better because it is more likely that
+        the server is appropriately configured.
        </para>
       </listitem>
      </varlistentry>