Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit31c5409

Browse files
committed
Remove bogus notice that older clients might not work with MD5 passwords.
That was written when we still had "crypt" authentication, and it wasreferring 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 withMD5 hashes, we'll need a similar notice again. But this text as it's wordednow is just wrong.)Backpatch to all supported versions.Discussion:https://www.postgresql.org/message-id/9a7263eb-0980-2072-4424-440bb2513dc7@iki.fi
1 parentde41869 commit31c5409

File tree

1 file changed

+0
-6
lines changed

1 file changed

+0
-6
lines changed

‎doc/src/sgml/ref/create_role.sgml

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -235,12 +235,6 @@ CREATE ROLE <replaceable class="PARAMETER">name</replaceable> [ [ WITH ] <replac
235235
password string). This allows reloading of encrypted
236236
passwords during dump/restore.
237237
</para>
238-
239-
<para>
240-
Note that older clients might lack support for the MD5
241-
authentication mechanism that is needed to work with passwords
242-
that are stored encrypted.
243-
</para>
244238
</listitem>
245239
</varlistentry>
246240

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp