Consistently mention 'SELECT pg_reload_conf()' in config files

bmomjian · bmomjian · commit 10c064ce4dad · 2016-10-25T11:26:15.000-04:00
Previously we only mentioned SIGHUP and 'pg_ctl reload' in
postgresql.conf and pg_hba.conf.
diff --git 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
 # ----------------------------------
 #
diff --git a/src/backend/utils/misc/postgresql.conf.sample b/src/backend/utils/misc/postgresql.conf.sample
@@ -16,9 +16,9 @@
 #
 # 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, or use "pg_ctl reload".  Some
-# parameters, which are marked below, require a server shutdown and restart to
-# take effect.
+# server for the changes to take effect, run "pg_ctl reload", or execute
+# "SELECT pg_reload_conf()".  Some parameters, which are marked below,
+# require a server shutdown and restart to take effect.
 #
 # Any parameter can also be given as a command-line option to the server, e.g.,
 # "postgres -c log_connections=on".  Some parameters can be changed at run time

Original file line number	Diff line number	Diff line change
`@@ -16,9 +16,9 @@`
`16`	`16`	`#`
`17`	`17`	`# This file is read on server startup and when the server receives a SIGHUP`
`18`	`18`	`# signal. If you edit the file on a running system, you have to SIGHUP the`
`19`		`-# server for the changes to take effect, or use "pg_ctl reload". Some`
`20`		`-# parameters, which are marked below, require a server shutdown and restart to`
`21`		`-# take effect.`
	`19`	`+# server for the changes to take effect, run "pg_ctl reload", or execute`
	`20`	`+# "SELECT pg_reload_conf()". Some parameters, which are marked below,`
	`21`	`+# require a server shutdown and restart to take effect.`
`22`	`22`	`#`
`23`	`23`	`# Any parameter can also be given as a command-line option to the server, e.g.,`
`24`	`24`	`# "postgres -c log_connections=on". Some parameters can be changed at run time`