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.

diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index 7889651e186ea90a9197c606a05fcc6049bc76f2..c1c7a2ab629e1449ec57fbcbe588cf842bf9f8fc 100644 (file)
--- 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).
+      
      
 
      
@@ -6937,7 +6944,7 @@
    PostgreSQL before version 8.1.
    It shows properties of all roles that are marked as
    rolcanlogin in
-   pg_authid.
+   pg_authid.
   
 
   
@@ -7004,7 +7011,9 @@
       passwd
       text
       
-      Password (possibly encrypted)
+      Password (possibly encrypted); null if none.  See
+      pg_authid
+      for details of how encrypted passwords are stored.