2006/3/6, Tom Lane <[EMAIL PROTECTED]>: > > The comment is referring to the control flow in a backend; you're > looking at the postmaster's sighup handler, which is different.
Then the following comment patch is appropriate, afaics. Markus Bertheau
Index: src/include/utils/guc.h =================================================================== RCS file: /projects/cvsroot/pgsql/src/include/utils/guc.h,v retrieving revision 1.64 diff -c -r1.64 guc.h *** src/include/utils/guc.h 5 Mar 2006 15:59:07 -0000 1.64 --- src/include/utils/guc.h 6 Mar 2006 17:58:59 -0000 *************** *** 31,40 **** * * 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.) * * BACKEND options can only be set at postmaster startup, from the * configuration file, or by client request in the connection startup --- 31,40 ---- * * 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 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
---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
