Update comment on how sighup signal affects postgresql.conf reload.

Markus Bertheau

diff --git a/src/include/utils/guc.h b/src/include/utils/guc.h
index 1068b6f0e73425e7b748ed459c1b322927a268a6..a55a89b90d8db1ccb65bbf91e13a6efa45c0f5e4 100644 (file)
--- a/src/include/utils/guc.h
+++ b/src/include/utils/guc.h
@@ -7,7 +7,7 @@
  * Copyright (c) 2000-2006, PostgreSQL Global Development Group
  * Written by Peter Eisentraut <peter_e@gmx.net>.
  *
- * $PostgreSQL: pgsql/src/include/utils/guc.h,v 1.64 2006/03/05 15:59:07 momjian Exp $
+ * $PostgreSQL: pgsql/src/include/utils/guc.h,v 1.65 2006/03/06 18:38:11 momjian Exp $
  *--------------------------------------------------------------------
  */
 #ifndef GUC_H
@@ -31,10 +31,10 @@
  *
  * SIGHUP options can only be set at postmaster startup or by changing
  * the configuration file and sending the HUP signal to the postmaster
- * or a backend process. (Notice that the signal receipt will not be
- * evaluated immediately. The postmaster and the backend check it at a
- * certain point in their main loop. It's safer to wait than to read a
- * file asynchronously.)
+ * or a backend process. (Notice that the signal receipt will be
+ * evaluated immediately only in the postmaster. The backend checks it
+ * at a certain point in its main loop. It's safer to wait than to
+ * read a file asynchronously.)
  *
  * BACKEND options can only be set at postmaster startup, from the
  * configuration file, or by client request in the connection startup