database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-11 10:01:57 +03:00
Code Activity

Put a tad more detail in the discussion of postmaster and postgres

Browse Source 
signal handling.
This commit is contained in:
Tom Lane
2003-09-18 20:30:15 +00:00
parent 723a9bde33
commit 689015748f
2 changed files with 26 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
doc/src/sgml/ref/postgres-ref.sgml
View File

@ -1,5 +1,5 @@
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.35 2003/08/31 17:32:24 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.36 2003/09/18 20:30:15 tgl Exp $
PostgreSQL documentation PostgreSQL documentation
--> -->
@ -365,13 +365,29 @@ PostgreSQL documentation
<title>Notes</title> <title>Notes</title>
<para> <para>
To stop a running query use the <literal>SIGINT</literal> signal. To To cancel a running query, send the <literal>SIGINT</literal> signal
tell <command>postgres</command> to reread the configuration file, to the <command>postgres</command> process running that command.
use a <literal>SIGHUP</literal> signal. The </para>
<command>postmaster</command> uses <literal>SIGTERM</literal>
<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>
The <command>postmaster</command> uses <literal>SIGTERM</literal>
to tell a <command>postgres</command> process to quit normally and to tell a <command>postgres</command> process to quit normally and
<literal>SIGQUIT</literal> to terminate without the normal cleanup. <literal>SIGQUIT</literal> to terminate without the normal cleanup.
These <emphasis>should not</emphasis> be used by users. These signals <emphasis>should not</emphasis> be used by users. It is also
unwise to send <literal>SIGKILL</literal> to a <command>postgres</command>
process --- the <command>postmaster</command> will interpret this as
a crash in <command>postgres</command>, and will force all the sibling
<command>postgres</command> processes to quit as part of its standard
crash-recovery procedure.
</para> </para>
</refsect1> </refsect1>

7
doc/src/sgml/ref/postmaster.sgml
View File

@ -1,5 +1,5 @@
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/postmaster.sgml,v 1.39 2003/09/12 00:12:47 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/postmaster.sgml,v 1.40 2003/09/18 20:30:15 tgl Exp $
PostgreSQL documentation PostgreSQL documentation
--> -->
@ -473,10 +473,11 @@ PostgreSQL documentation
<para> <para>
If at all possible, <emphasis>do not</emphasis> use If at all possible, <emphasis>do not</emphasis> use
<literal>SIGKILL</literal> to kill the <literal>SIGKILL</literal> to kill the
<command>postmaster</command>. This will prevent <command>postmaster</command>. Doing so will prevent
<command>postmaster</command> from freeing the system <command>postmaster</command> from freeing the system
resources (e.g., shared memory and semaphores) that it holds before resources (e.g., shared memory and semaphores) that it holds before
terminating. terminating. This may cause problems for starting a fresh
<command>postmaster</command> run.
</para> </para>
<para> <para>