Wording improvements to runtime.sgml. Add mention in postgresql.conf

file that SIGHUP or "pg_ctl reload" are required for changes to take
affect on a running server.
ecpg_big_bison
Bruce Momjian 24 years ago
parent db1d7a9ada
commit fdcb8516d4
  1. 1124
      doc/src/sgml/runtime.sgml
  2. 20
      src/backend/utils/misc/postgresql.conf.sample

File diff suppressed because it is too large Load Diff

@ -2,19 +2,23 @@
# PostgreSQL configuration file # PostgreSQL configuration file
# ----------------------------- # -----------------------------
# #
# This file consists of lines of the form # This file consists of lines of the form:
# #
# name = value # name = value
# #
# (The `=' is optional.) White space is collapsed, comments are # (The '=' is optional.) White space may be used. Comments are introduced
# introduced by `#' anywhere on a line. The complete list of option # with '#' anywhere on a line. The complete list of option names and
# names and allowed values can be found in the PostgreSQL # allowed values can be found in the PostgreSQL documentation. The
# documentation. The commented-out settings shown in this file # commented-out settings shown in this file represent the default values.
# represent the default values. #
# Any option can also be given as a command line switch to the # Any option can also be given as a command line switch to the
# postmaster, e.g., 'postmaster -c log_connections=on'. Some options # postmaster, e.g. 'postmaster -c log_connections=on'. Some options
# can be changed at run-time with the 'SET' SQL command. # can be changed at run-time with the 'SET' SQL command.
#
# This file is read on postmaster startup and when the postmaster
# receives a SIGHUP. If you edit the file on a running system, you have
# to SIGHUP the postmaster for the changes to take effect, or use
# "pg_ctl reload".
#======================================================================== #========================================================================

Loading…
Cancel
Save