From: Peter Eisentraut <peter@eisentraut.org>
Date: Sat, 9 Nov 2019 09:13:14 +0000 (+0100)
Subject: doc: Clarify documentation about SSL passphrases
X-Git-Tag: REL_11_6~6
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=f77be47d339898aeab97ba3fb6c649512e34cab7;p=thirdparty%2Fpostgresql.git

doc: Clarify documentation about SSL passphrases

The previous statement that using a passphrase disables the ability to
change the server's SSL configuration without a server restart was no
longer completely true since the introduction of
ssl_passphrase_command_supports_reload.
---

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 333adda4086..f16bc455822 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -2246,8 +2246,9 @@ pg_dumpall -p 5432 | psql -d postgres -p 5433
    If the private key is protected with a passphrase, the
    server will prompt for the passphrase and will not start until it has
    been entered.
-   Using a passphrase also disables the ability to change the server's SSL
-   configuration without a server restart.
+   Using a passphrase by default disables the ability to change the server's
+   SSL configuration without a server restart, but see <xref
+   linkend="guc-ssl-passphrase-command-supports-reload"/>.
    Furthermore, passphrase-protected private keys cannot be used at all
    on Windows.
   </para>