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

Markus Bertheau
This commit is contained in:
Bruce Momjian 2006-03-06 18:38:11 +00:00
parent 526f773d2f
commit a9c1047ebd
1 changed files with 5 additions and 5 deletions

View File

@ -7,7 +7,7 @@
* Copyright (c) 2000-2006, PostgreSQL Global Development Group * Copyright (c) 2000-2006, PostgreSQL Global Development Group
* Written by Peter Eisentraut <peter_e@gmx.net>. * 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 #ifndef GUC_H
@ -31,10 +31,10 @@
* *
* SIGHUP options can only be set at postmaster startup or by changing * SIGHUP options can only be set at postmaster startup or by changing
* the configuration file and sending the HUP signal to the postmaster * the configuration file and sending the HUP signal to the postmaster
* or a backend process. (Notice that the signal receipt will not be * or a backend process. (Notice that the signal receipt will be
* evaluated immediately. The postmaster and the backend check it at a * evaluated immediately only in the postmaster. The backend checks it
* certain point in their main loop. It's safer to wait than to read a * at a certain point in its main loop. It's safer to wait than to
* file asynchronously.) * read a file asynchronously.)
* *
* BACKEND options can only be set at postmaster startup, from the * BACKEND options can only be set at postmaster startup, from the
* configuration file, or by client request in the connection startup * configuration file, or by client request in the connection startup