From: Bruce Momjian <bruce@momjian.us>
Date: Wed, 22 Aug 2012 16:00:24 +0000 (-0400)
Subject: Document that pg_reload_conf() is also an easy way to reload the
X-Git-Tag: REL9_3_BETA1~1044
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=7dff5b8edd898146ffa4afc2df3f9d5c67e43f0e;p=postgresql

Document that pg_reload_conf() is also an easy way to reload the
configuration file.
---

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 7727ea7f89..59902ed86c 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -116,9 +116,10 @@ include 'filename'
       <primary>SIGHUP</primary>
      </indexterm>
      The configuration file is reread whenever the main server process
-     receives a
-     <systemitem>SIGHUP</> signal (which is most easily sent by means
-     of <literal>pg_ctl reload</>). The main server process
+     receives a <systemitem>SIGHUP</> signal;  this is most easily done by
+     running <literal>pg_ctl reload</> from the command-line or by calling
+     the SQL function <function>pg_reload_conf()</function>). The main
+     server process
      also propagates this signal to all currently running server
      processes so that existing sessions also get the new
      value. Alternatively, you can send the signal to a single server