summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHeikki Linnakangas2017-01-03 12:09:01 +0000
committerHeikki Linnakangas2017-01-03 12:09:01 +0000
commit31c54096a18f5ae4ebf8ac9e86963b2b36f2abb5 (patch)
tree5a154c6fe1f3120f255ac5f45017a33e7b9b05be
parentde41869b64d57160f58852eab20a27f248188135 (diff)
Remove bogus notice that older clients might not work with MD5 passwords.
That was written when we still had "crypt" authentication, and it was referring to the fact that an older client might support "crypt" authentication but not "md5". But we haven't supported "crypt" for years. (As soon as we add a new authentication mechanism that doesn't work with MD5 hashes, we'll need a similar notice again. But this text as it's worded now is just wrong.) Backpatch to all supported versions. Discussion: https://www.postgresql.org/message-id/[email protected]
-rw-r--r--doc/src/sgml/ref/create_role.sgml6
1 files changed, 0 insertions, 6 deletions
diff --git a/doc/src/sgml/ref/create_role.sgml b/doc/src/sgml/ref/create_role.sgml
index 38cd4c8369..a3b8ed9ab4 100644
--- a/doc/src/sgml/ref/create_role.sgml
+++ b/doc/src/sgml/ref/create_role.sgml
@@ -235,12 +235,6 @@ CREATE ROLE <replaceable class="PARAMETER">name</replaceable> [ [ WITH ] <replac
password string). This allows reloading of encrypted
passwords during dump/restore.
</para>
-
- <para>
- Note that older clients might lack support for the MD5
- authentication mechanism that is needed to work with passwords
- that are stored encrypted.
- </para>
</listitem>
</varlistentry>