aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/functions.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2020-11-18 10:28:50 +0200
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2020-11-18 10:28:50 +0200
commitdfab7f2f94812c6c3a62cfde0ec7f9e447132e64 (patch)
treebcfeb3bf9caf5442cd69ff284fbea2dcd3bc5ce9 /src/backend/executor/functions.c
parent6dd8b00807871bfd0c3ce8e18fd1f6ba1a71fbf9 (diff)
downloadpostgresql-dfab7f2f94812c6c3a62cfde0ec7f9e447132e64.tar.gz
postgresql-dfab7f2f94812c6c3a62cfde0ec7f9e447132e64.zip
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
Diffstat (limited to 'src/backend/executor/functions.c')
0 files changed, 0 insertions, 0 deletions