Update sample error messages to agree with current code.

diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index af603a62e8393ff6b1cf044a4fa1189abe6dc0d0..4fe4b256aa26a83b201ed92ea18c31a5469b5401 100644 (file)
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  Client Authentication
@@ -56,7 +56,7 @@
    of a set of records, one per line. Blank lines and lines beginning
    with a hash character (#) are ignored. A record is
    made up of a number of fields which are separated by spaces and/or
-   tabs and cannot be continued across several lines.
+   tabs.  Records cannot be continued across lines.
   
 
   
@@ -85,7 +85,7 @@ hostssl database IP-address
       
        This record pertains to connection attempts over TCP/IP
        networks. Note that TCP/IP connections are completely disabled
-       unless the server is started with the -i or
+       unless the server is started with the -i switch or
        the equivalent configuration parameter is set.
       
      
@@ -234,6 +234,7 @@ hostssl database IP-address
           of the connecting user. Postgres
           then verifies whether the so identified operating system user
           is allowed to connect as the database user that is requested.
+     This is only available for TCP/IP connections.
           The authentication option following
           the ident keyword specifies the name of an
           ident map that specifies which operating
@@ -507,7 +508,7 @@ host         all        192.168.0.0    255.255.0.0        ident     omicron
    
     The Identification Protocol is described in
     RFC 1413. Virtually every Unix-like
-    operating systems ships with an ident server that listens on TCP
+    operating system ships with an ident server that listens on TCP
     port 113 by default. The basic functionality of an ident server
     is to answer questions like What user initiated the
     connection that goes out of your port X
@@ -628,14 +629,14 @@ Password authentication failed for user 'joeblow'
 
    
 
-FATAL 1:  SetUserId: user 'joeblow' is not in 'pg_shadow'
+FATAL 1:  user "joeblow" does not exist
 
-    This is the fancy way of saying that the user doesn't exist at all.
+    The indicated user name was not found in pg_shadow.
    
 
    
 
-FATAL 1:  Database testdb does not exist in pg_database
+FATAL 1:  Database "testdb" does not exist in the system catalog.
 
     The database you're trying to connect to doesn't exist. Note that
     if you don't specify a database name, it defaults to the database