Add mention of SIGHUP on the postmaster manual page.

diff --git a/doc/src/sgml/ref/postgres-ref.sgml b/doc/src/sgml/ref/postgres-ref.sgml
index 279d8875e0ee58881a7c6887f07fd462a33f404c..d558782e63b8e98bee8575cc38af9856d825753f 100644 (file)
--- a/doc/src/sgml/ref/postgres-ref.sgml
+++ b/doc/src/sgml/ref/postgres-ref.sgml
@@ -1,5 +1,5 @@
 
 
@@ -370,12 +370,12 @@ PostgreSQL documentation
   
 
   
-   To tell postgres to reread the configuration file,
+   To tell postgres to reload the configuration files,
    send a SIGHUP signal.  Normally it's best to
    SIGHUP the postmaster instead;
    the postmaster will in turn SIGHUP
    each of its children.  But in some cases it might be desirable to have only
-   one postgres process reread the configuration file.
+   one postgres process reload the configuration files.
   
 
   

diff --git a/doc/src/sgml/ref/postmaster.sgml b/doc/src/sgml/ref/postmaster.sgml
index f4ec3c98986e5e38b52333574edc7f414ab03721..f5a8aa3ca3147aff6e70118a7c4f97e3fa02888e 100644 (file)
--- a/doc/src/sgml/ref/postmaster.sgml
+++ b/doc/src/sgml/ref/postmaster.sgml
@@ -1,5 +1,5 @@
 
 
@@ -487,7 +487,8 @@ PostgreSQL documentation
    all clients to terminate before quitting, the second will
    forcefully disconnect all clients, and the third will quit
    immediately without proper shutdown, resulting in a recovery run
-   during restart.
+   during restart.   The SIGHUP signal will 
+   reload the server configuration files.