To: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
From: Ian Barwick <ian.barwick@2ndquadrant.com>
Subject: doc: mention pg_reload_conf() in pg_hba.conf documentation
Message-ID: <538950ec-b86a-1650-6078-beb7091c09c2@2ndquadrant.com>
Date: Mon, 15 Jul 2019 12:47:18 +0900
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.7.0
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="------------7959B5ADDBB26CFA331A6FA8"
Content-Language: en-US
Precedence: bulk

This is a multi-part message in MIME format.
--------------7959B5ADDBB26CFA331A6FA8
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi

I noticed the documentation for pg_hba.conf:

   https://www.postgresql.org/docs/current/auth-pg-hba-conf.html

says:

     you will need to signal the postmaster (using pg_ctl reload or kill -HUP) to
     make it re-read the file.

It would be useful to mention pg_reload_conf() as another option here, as done
elsewhere in the docs.

Patch with suggested change attached.


Regards

Ian Barwick


-- 
  Ian Barwick                   https://www.2ndQuadrant.com/
  PostgreSQL Development, 24x7 Support, Training & Services

--------------7959B5ADDBB26CFA331A6FA8
Content-Type: text/x-patch;
 name="doc-pg_hba-pg_reload_conf.v1.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="doc-pg_hba-pg_reload_conf.v1.patch"

diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
new file mode 100644
index 3ed74d8..c90ca0b
*** a/doc/src/sgml/client-auth.sgml
--- b/doc/src/sgml/client-auth.sgml
*************** hostnogssenc <replaceable>database</repl
*** 650,657 ****
     <systemitem>SIGHUP</systemitem><indexterm><primary>SIGHUP</primary></indexterm>
     signal. If you edit the file on an
     active system, you will need to signal the postmaster
!    (using <literal>pg_ctl reload</literal> or <literal>kill -HUP</literal>) to make it
!    re-read the file.
    </para>
  
    <note>
--- 650,658 ----
     <systemitem>SIGHUP</systemitem><indexterm><primary>SIGHUP</primary></indexterm>
     signal. If you edit the file on an
     active system, you will need to signal the postmaster
!    (using <literal>pg_ctl reload</literal>, <literal>kill -HUP</literal>
!    or by calling the SQL function <function>pg_reload_conf()</function>)
!    to make it re-read the file.
    </para>
  
    <note>

--------------7959B5ADDBB26CFA331A6FA8--