postgresql.conf and pg_ctl reload - Mailing list pgsql-admin

From litaowu@yahoo.com (Litao Wu)
Subject postgresql.conf and pg_ctl reload
Date
Msg-id a807f176.0403190941.39f9522b@posting.google.com
Whole thread Raw
List pgsql-admin
Hi all,

postgresql.conf says:
# 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".

Does that mean I can just use "pg_ctl reload" to let the changed
parameters take affect? Or do I have to restart postgres? Or only some
parameters can be taken affect by "pg_ctl reload" (if this case, what are they)?


Same question from man page of pg_ctl:
pg_ctl reload  -
  simply sends the postmaster a SIGHUP signal, causing  it  to  reread
  its  configuration  files  (postgresql.conf,  pg_hba.conf,  etc.).
  This allows changing of configuration-file options that do not require a
  complete restart to take effect.

The problem is which options do not require a complete restart and which ones do?

Thanks,

pgsql-admin by date:

Previous
From: "Luz Aida Uribe Velez"
Date:
Subject: Differential Backup
Next
From: Dohyung Kim
Date:
Subject: what the initial 3 daemon of postmaster process do?