From 3b927be5153eabe892d63eff2de4df1706735ca2 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Thu, 16 Oct 2003 17:38:01 +0000 Subject: [PATCH] Add mention of SIGHUP on the postmaster manual page. --- doc/src/sgml/ref/postgres-ref.sgml | 4 ++-- doc/src/sgml/ref/postmaster.sgml | 3 ++- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/ref/postgres-ref.sgml b/doc/src/sgml/ref/postgres-ref.sgml index cdd3248c6c..c36505af36 100644 --- a/doc/src/sgml/ref/postgres-ref.sgml +++ b/doc/src/sgml/ref/postgres-ref.sgml @@ -370,12 +370,12 @@ PostgreSQL documentation - To tell postgres to reread the configuration file, + 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 reread the configuration file. + one postgres process reload the configuration files. diff --git a/doc/src/sgml/ref/postmaster.sgml b/doc/src/sgml/ref/postmaster.sgml index fb27b605a9..90e1a82442 100644 --- a/doc/src/sgml/ref/postmaster.sgml +++ b/doc/src/sgml/ref/postmaster.sgml @@ -487,7 +487,8 @@ PostgreSQL documentation 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. + during restart. The SIGHUP signal will + reload the server configuration files. -- 2.39.5