Add documentation changes for new pg_hba.conf behavior.

diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index 230bceb45fb949e77b9863c29f85fd9a97482841..bb5a560ad67f0125472a81423804021d7cd9ffd0 100644 (file)
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  Client Authentication
@@ -280,9 +280,10 @@ hostssl database IP-address
   
 
   
-   The pg_hba.conf file is re-read during each
-   connection attempt. It is therefore trivial to modify access
-   permissions while the server is running: just edit the file.
+   The pg_hba.conf file is loaded only on startup
+   and when the postmaster receives a SIGHUP signal. If
+   you edit the file on an active system, you will need to issue a
+   SIGHUP to the postmaster using kill.
   
 
   

diff --git a/src/backend/libpq/pg_hba.conf.sample b/src/backend/libpq/pg_hba.conf.sample
index da9133a83ec19d8556029b88b243e3f06db2be46..9c8d8ae74d5b7c82bdec4e7b3e5649e952cba912 100644 (file)
--- a/src/backend/libpq/pg_hba.conf.sample
+++ b/src/backend/libpq/pg_hba.conf.sample
@@ -8,8 +8,9 @@
 #  o how users are authenticated on each host
 #  o databases accessible by each host
 # 
-# It is read by the PostgreSQL postmaster each time a host tries to make a
-# connection to a database.
+# It is read on postmaster startup and when the postmaster receives a SIGHUP.
+# If you edit the file on a running system, you have to SIGHUP the postmaster
+# for the changes to take effect.
 # 
 # Each line is a new record. Records cannot be continued across multiple
 # lines. Comments begin with # and continue to the end of the line.