From 9ad637f749b8e26eb3e0c0f3cb6bb1512c40aee9 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 16 Oct 2003 17:38:01 +0000
Subject: [PATCH] Add mention of SIGHUP on the postmaster manual page.

---
 doc/src/sgml/ref/postgres-ref.sgml | 6 +++---
 doc/src/sgml/ref/postmaster.sgml   | 5 +++--
 2 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/doc/src/sgml/ref/postgres-ref.sgml b/doc/src/sgml/ref/postgres-ref.sgml
index 279d8875e0e..d558782e63b 100644
--- a/doc/src/sgml/ref/postgres-ref.sgml
+++ b/doc/src/sgml/ref/postgres-ref.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.37 2003/09/24 18:54:01 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.38 2003/10/16 17:38:01 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -370,12 +370,12 @@ PostgreSQL documentation
   </para>
 
   <para>
-   To tell <command>postgres</command> to reread the configuration file,
+   To tell <command>postgres</command> to reload the configuration files,
    send a <literal>SIGHUP</literal> signal.  Normally it's best to
    <literal>SIGHUP</literal> the <command>postmaster</command> instead;
    the <command>postmaster</command> will in turn <literal>SIGHUP</literal>
    each of its children.  But in some cases it might be desirable to have only
-   one <command>postgres</command> process reread the configuration file.
+   one <command>postgres</command> process reload the configuration files.
   </para>
 
   <para>
diff --git a/doc/src/sgml/ref/postmaster.sgml b/doc/src/sgml/ref/postmaster.sgml
index f4ec3c98986..f5a8aa3ca31 100644
--- a/doc/src/sgml/ref/postmaster.sgml
+++ b/doc/src/sgml/ref/postmaster.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/postmaster.sgml,v 1.40 2003/09/18 20:30:15 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/postmaster.sgml,v 1.41 2003/10/16 17:38:01 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -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 <literal>SIGHUP</literal> signal will 
+   reload the server configuration files.
   </para>
 
   <para>