Remove bogus notice that older clients might not work with MD5 passwords.
authorHeikki Linnakangas <[email protected]>
Tue, 3 Jan 2017 12:09:01 +0000 (14:09 +0200)
committerHeikki Linnakangas <[email protected]>
Tue, 3 Jan 2017 12:10:10 +0000 (14:10 +0200)
commit7e3ae545594874d853e358fffe029c6266509727
treec984c21c0e04f153f2e3148c17c65f440cf9e08f
parentfce04516ec5e34dcad18d1dc60e1373a292c218e
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/9a7263eb-0980-2072-4424-440bb2513dc7@iki.fi
doc/src/sgml/ref/create_role.sgml