doc: mention pg_reload_conf() for reloading the config file

Reported-by: Ian Barwick
Discussion: https://postgr.es/m/538950ec-b86a-1650-6078-beb7091c09c2@2ndquadrant.com

Backpatch-through: 9.4

diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index e7c80b912b7779a087f869ce34d419c7780a1bbd..f8d55b20efe78ec990c6418b624a488e0ed5d685 100644 (file)
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -572,8 +572,9 @@ hostnossl  database  user
    SIGHUPSIGHUP
    signal. If you edit the file on an
    active system, you will need to signal the postmaster
-   (using pg_ctl reload or kill -HUP) to make it
-   re-read the file.
+   (using pg_ctl reload, calling the SQL function
+   pg_reload_conf(), or using kill
+   -HUP) to make it re-read the file.
   
 
   
@@ -767,8 +768,9 @@ mymap   /^(.*)@otherdomain\.com$   guest
    SIGHUPSIGHUP
    signal. If you edit the file on an
    active system, you will need to signal the postmaster
-   (using pg_ctl reload or kill -HUP) to make it
-   re-read the file.
+   (using pg_ctl reload, calling the SQL function
+   pg_reload_conf(), or using kill
+   -HUP) to make it re-read the file.