From dfab7f2f94812c6c3a62cfde0ec7f9e447132e64 Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas Date: Wed, 18 Nov 2020 10:28:50 +0200 Subject: [PATCH] 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 --- doc/src/sgml/func.sgml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 7c7d177c02..df2c1c6f05 100644 --- 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.