public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: PostgreSQL-documentation <[email protected]>
Subject: Missing documention on SIGHUP
Date: Thu, 16 Oct 2003 13:37:45 -0400 (EDT)
Message-ID: <[email protected]> (raw)
I see there is no mention of SIGHUP in the postmaster manual page. It
is mentioned in the postgres manual page, though.
This patch adds the mention.
--
Bruce Momjian | http://candle.pha.pa.us
[email protected] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
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 ****
</para>
<para>
! To tell <command>postgres</command> to reread the configuration file,
send a <literal>SIGHUP</literal> signal. Normally it's best to
<literal>SIGHUP</literal> the <command>postmaster</command> instead;
the <command>postmaster</command> will in turn <literal>SIGHUP</literal>
each of its children. But in some cases it might be desirable to have only
! one <command>postgres</command> process reread the configuration file.
</para>
<para>
--- 370,381 ----
</para>
<para>
! To tell <command>postgres</command> to reload the configuration files,
send a <literal>SIGHUP</literal> signal. Normally it's best to
<literal>SIGHUP</literal> the <command>postmaster</command> instead;
the <command>postmaster</command> will in turn <literal>SIGHUP</literal>
each of its children. But in some cases it might be desirable to have only
! one <command>postgres</command> process reload the configuration files.
</para>
<para>
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.
</para>
<para>
--- 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 <literal>SIGHUP</literal> signal will
! reload the server configuration files.
</para>
<para>
Attachments:
[text/plain] /bjm/diff (2.4K, 2-%2Fbjm%2Fdiff)
download | inline:
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 ****
</para>
<para>
! To tell <command>postgres</command> to reread the configuration file,
send a <literal>SIGHUP</literal> signal. Normally it's best to
<literal>SIGHUP</literal> the <command>postmaster</command> instead;
the <command>postmaster</command> will in turn <literal>SIGHUP</literal>
each of its children. But in some cases it might be desirable to have only
! one <command>postgres</command> process reread the configuration file.
</para>
<para>
--- 370,381 ----
</para>
<para>
! To tell <command>postgres</command> to reload the configuration files,
send a <literal>SIGHUP</literal> signal. Normally it's best to
<literal>SIGHUP</literal> the <command>postmaster</command> instead;
the <command>postmaster</command> will in turn <literal>SIGHUP</literal>
each of its children. But in some cases it might be desirable to have only
! one <command>postgres</command> process reload the configuration files.
</para>
<para>
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.
</para>
<para>
--- 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 <literal>SIGHUP</literal> signal will
! reload the server configuration files.
</para>
<para>
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: Missing documention on SIGHUP
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox