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
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>
