mirror/postgresql
2
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-12-27 08:39:28 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: Clarify that signal functions have no feedback.

Browse Source 
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
This commit is contained in:
Heikki Linnakangas 2020-11-18 10:28:50 +02:00
parent 6dd8b00807
commit dfab7f2f94
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/src/sgml/func.sgml
View File

@ -23922,7 +23922,8 @@ SELECT collation for ('foo' COLLATE "de_DE");
<para>
Each of these functions returns <literal>true</literal> if
successful and <literal>false</literal> otherwise.
the signal was successfully sent and <literal>false</literal>
if sending the signal failed.
</para>
<table id="functions-admin-signal-table">
@ -23970,7 +23971,10 @@ SELECT collation for ('foo' COLLATE "de_DE");
server to reload their configuration files. (This is initiated by
sending a <systemitem>SIGHUP</systemitem> signal to the postmaster
process, which in turn sends <systemitem>SIGHUP</systemitem> to each
of its children.)
of its children.) You can use the
<link linkend="view-pg-file-settings">pg_file_settings</link> and
<link linkend="view-pg-hba-file-rules">pg_hba_file_rules</link> views
to check the configuration files for possible errors, before reloading.
</para></entry>
</row>