docs: Clarify that signal functions have no feedback.

Bug #16652 complains that pg_reload_conf() returned true, even though
the configuration file contained errors. That's the way pg_reload_conf()
works, by design, but the documentation wasn't very clear on it. Clarify
that a 'true' return value only means that the signal was sent
successfully. Also add links to the system views that can be used to
check the configuration files for errors.

David G. Johnston, with some rewording by me.

Discussion: https://www.postgresql.org/message-id/CAKFQuwax6GxhUQEes0D045UtXG-fBraM39_6UMd5JyR5K1HWCQ%40mail.gmail.com

diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 7c7d177c022829bcb16e855e75b96e92d948ad0e..df2c1c6f053bf20b356b1e84629cb3b9d20904fe 100644 (file)
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -23922,7 +23922,8 @@ SELECT collation for ('foo' COLLATE "de_DE");
 
    
     Each of these functions returns true if
-    successful and false otherwise.
+    the signal was successfully sent and false
+    if sending the signal failed.
    
 
    
@@ -23970,7 +23971,10 @@ SELECT collation for ('foo' COLLATE "de_DE");
         server to reload their configuration files.  (This is initiated by
         sending a SIGHUP signal to the postmaster
         process, which in turn sends SIGHUP to each
-        of its children.)
+        of its children.) You can use the
+        pg_file_settings and
+        pg_hba_file_rules views
+        to check the configuration files for possible errors, before reloading.