On Mon, Jul 15, 2019 at 12:47:18PM +0900, Ian Barwick wrote:
> 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.
Oh, good point. Not sure how we missed that, but I had to fix a mention
in pg_hba.conf a while ago too. Also, there were two mentions in that
file, so I fixed them both with the attached patch. Backpatched to 9.4.
--
Bruce Momjian <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
new file mode 100644
index 3ed74d8..fada728
*** 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>, calling the SQL function
! <function>pg_reload_conf()</function>, or using <literal>kill
! -HUP</literal>) to make it re-read the file.
</para>
<note>
*************** mymap /^(.*)@otherdomain\.com$ guest
*** 871,878 ****
<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>
<para>
--- 872,880 ----
<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>, calling the SQL function
! <function>pg_reload_conf()</function>, or using <literal>kill
! -HUP</literal>) to make it re-read the file.
</para>
<para>
