From 10c064ce4dad088ba2d8b978bff6009b9f22dc3a Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 25 Oct 2016 11:26:15 -0400 Subject: 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. --- src/backend/utils/misc/postgresql.conf.sample | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'src/backend/utils/misc/postgresql.conf.sample') diff --git a/src/backend/utils/misc/postgresql.conf.sample b/src/backend/utils/misc/postgresql.conf.sample index 159ada3bc63..cf3400538a0 100644 --- 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 -- cgit v1.2.3