From d7a541a9a7927b2478084e7d20a026cb87dcfa3b Mon Sep 17 00:00:00 2001 From: Robert Haas Date: Mon, 13 Sep 2010 17:02:34 +0000 Subject: [PATCH] Elaborate on what gets stored in pg_authid.rolpasswd. Also, add cross-reference from pg_shadow.passwd to pg_authid.rolpasswd and fix a bit of markup I muffed in my previous commit. Per discussion with Josh Kupershmidt. --- doc/src/sgml/catalogs.sgml | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index c7828e897ee..06c6509b77f 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -1,4 +1,4 @@ - + @@ -1179,7 +1179,14 @@ rolpassword text - Password (possibly encrypted); null if none + + Password (possibly encrypted); null if none. If the password is + encrypted, this column will contain the string md5 followed by a + 32-character hexadecimal MD5 hash. The MD5 hash will be of the + user's password concatenated to their username (for example, if + user joe has password xyzzy, PostgreSQL will store + the md5 hash of xyzzyjoe). + @@ -6938,7 +6945,7 @@ PostgreSQL before version 8.1. It shows properties of all roles that are marked as rolcanlogin in - pg_authid. + pg_authid. @@ -7005,7 +7012,9 @@ passwd text - Password (possibly encrypted) + Password (possibly encrypted); null if none. See + pg_authid + for details of how encrypted passwords are stored.