Back out libpq changes for service --- not ready yet.

diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 48e9a2de3fd841973f8386667c5edd8d066a6c70..8362208600defbf36cd0ef210542a0536dd30fea 100644 (file)
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -1,5 +1,5 @@
 
 
  
@@ -4031,57 +4031,6 @@ however.)
 
 
 
-
-The Connection Service File
-
-
- connection service file
-
-
- pg_service.conf
-
-
-
-The file pg_service.conf in the sysconf
-directory (typically /usr/local/pgsql/etc) can assocate a 
-group of libpq connection parameters with a single service name that
-can be specified in the libpq connection.
-.   a user's home directory or the
-file referenced by PGPASSFILE can contain passwords to
-be used if the connection requires a password (and no password has been
-specified  otherwise). On Microsoft Windows the file is named
-%APPDATA%\postgresql\pgpass.conf (where
-%APPDATA% refers to the Application Data subdirectory in
-the user's profile).
-
-
-
-This file should contain lines of the following format:
-
-hostname:port:database:username:password
-
-Each of the first four fields may be a literal value, or *,
-which matches anything.  The password field from the first line that matches the
-current connection parameters will be used.  (Therefore, put more-specific
-entries first when you are using wildcards.)
-If an entry needs to contain : or
-\, escape this character with \.
-A hostname of localhost matches both host (TCP)
-and local (Unix domain socket) connections coming from the
-local machine.
-
-
-
-The permissions on .pgpass must disallow any
-access to world or group; achieve this by the command
-chmod 0600 ~/.pgpass.
-If the permissions are less strict than this, the file will be ignored.
-(The file permissions are not currently checked on Microsoft Windows,
-however.)
-
-
-
-
 
 SSL Support