summaryrefslogtreecommitdiff
path: root/src/backend/libpq
diff options
context:
space:
mode:
authorBruce Momjian2016-10-25 15:26:15 +0000
committerBruce Momjian2016-10-25 15:26:15 +0000
commit10c064ce4dad088ba2d8b978bff6009b9f22dc3a (patch)
tree9ed70b3db9a3631d103bcea041559e22cc75267c /src/backend/libpq
parentf5d6bce63ceb3c59a964814bb0df5a0648e750e5 (diff)
Consistently mention 'SELECT pg_reload_conf()' in config files
Previously we only mentioned SIGHUP and 'pg_ctl reload' in postgresql.conf and pg_hba.conf.
Diffstat (limited to 'src/backend/libpq')
-rw-r--r--src/backend/libpq/pg_hba.conf.sample10
1 files changed, 5 insertions, 5 deletions
diff --git a/src/backend/libpq/pg_hba.conf.sample b/src/backend/libpq/pg_hba.conf.sample
index 86a89edf9a..e0fbfcb026 100644
--- a/src/backend/libpq/pg_hba.conf.sample
+++ b/src/backend/libpq/pg_hba.conf.sample
@@ -59,11 +59,11 @@
# its special character, and just match a database or username with
# that name.
#
-# This file is read on server startup and when the postmaster receives
-# a SIGHUP signal. If you edit the file on a running system, you have
-# to SIGHUP the postmaster for the changes to take effect. You can
-# use "pg_ctl reload" to do that.
-
+# This file is read on server startup and when the server receives a
+# SIGHUP signal. If you edit the file on a running system, you have to
+# SIGHUP the server for the changes to take effect, run "pg_ctl reload",
+# or execute "SELECT pg_reload_conf()".
+#
# Put your actual configuration here
# ----------------------------------
#