I found our postgresql.conf and pg_hba.conf config files had inconsistent comment instructions about reloading, and didn't mention SELECT pg_reload_conf().
The attached doc patch fixes this. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
diff --git a/src/backend/libpq/pg_hba.conf.sample b/src/backend/libpq/pg_hba.conf.sample new file mode 100644 index 86a89ed..e0fbfcb *** a/src/backend/libpq/pg_hba.conf.sample --- b/src/backend/libpq/pg_hba.conf.sample *************** *** 59,69 **** # 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. ! # Put your actual configuration here # ---------------------------------- # --- 59,69 ---- # its special character, and just match a database or username with # that name. # ! # 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 new file mode 100644 index 159ada3..cf34005 *** a/src/backend/utils/misc/postgresql.conf.sample --- b/src/backend/utils/misc/postgresql.conf.sample *************** *** 16,24 **** # # 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. # # 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 --- 16,24 ---- # # 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()". 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
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
