Index: doc/src/sgml/ref/postgres-ref.sgml =================================================================== RCS file: /cvsroot/pgsql-server/doc/src/sgml/ref/postgres-ref.sgml,v retrieving revision 1.37 diff -c -c -r1.37 postgres-ref.sgml *** doc/src/sgml/ref/postgres-ref.sgml 24 Sep 2003 18:54:01 -0000 1.37 --- doc/src/sgml/ref/postgres-ref.sgml 16 Oct 2003 17:30:52 -0000 *************** *** 370,381 **** ! To tell postgres to reread the configuration file, send a SIGHUP signal. Normally it's best to SIGHUP the postmaster instead; the postmaster will in turn SIGHUP each of its children. But in some cases it might be desirable to have only ! one postgres process reread the configuration file. --- 370,381 ---- ! To tell postgres to reload the configuration files, send a SIGHUP signal. Normally it's best to SIGHUP the postmaster instead; the postmaster will in turn SIGHUP each of its children. But in some cases it might be desirable to have only ! one postgres process reload the configuration files. Index: doc/src/sgml/ref/postmaster.sgml =================================================================== RCS file: /cvsroot/pgsql-server/doc/src/sgml/ref/postmaster.sgml,v retrieving revision 1.40 diff -c -c -r1.40 postmaster.sgml *** doc/src/sgml/ref/postmaster.sgml 18 Sep 2003 20:30:15 -0000 1.40 --- doc/src/sgml/ref/postmaster.sgml 16 Oct 2003 17:30:52 -0000 *************** *** 487,493 **** all clients to terminate before quitting, the second will forcefully disconnect all clients, and the third will quit immediately without proper shutdown, resulting in a recovery run ! during restart. --- 487,494 ---- all clients to terminate before quitting, the second will forcefully disconnect all clients, and the third will quit immediately without proper shutdown, resulting in a recovery run ! during restart. The SIGHUP signal will ! reload the server configuration files.