diff options
| author | Peter Eisentraut | 2019-11-09 09:13:14 +0000 |
|---|---|---|
| committer | Peter Eisentraut | 2019-11-09 09:14:55 +0000 |
| commit | 4977a35ea79a4608a2617a06bb73488f199d062f (patch) | |
| tree | 6ed8c758e9e83064aa2de59ff7c3592073c004dd | |
| parent | 175571923c5c6f2ddd0e8f0fae726acda8a9e067 (diff) | |
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.
| -rw-r--r-- | doc/src/sgml/runtime.sgml | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 112ae591dc3..a34d31d297a 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -2310,8 +2310,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> |