mirror/postgresql
2
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2025-01-24 18:55:04 +08:00
Code Issues Packages Projects Releases Wiki Activity

Properly document that SIGTERM is OK for users to use on a postgres

Browse Source 
session, now that pg_terminate_backend() uses it.

Josh Kupershmidt
This commit is contained in:
Bruce Momjian 2012-08-30 17:58:36 -04:00
parent 39d0653d05
commit b5dc7612a5
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -732,14 +732,18 @@ PostgreSQL documentation
<para>
To cancel a running query, send the <literal>SIGINT</literal> signal
to the process running that command.
to the process running that command. To terminate a backend process
cleanly, send <literal>SIGTERM</literal> to that process. See
also <function>pg_cancel_backend</> and <function>pg_terminate_backend</>
in <xref linkend="functions-admin-signal"> for the SQL-callable equivalents
of these two actions.
</para>
<para>
The <command>postgres</command> server uses <literal>SIGTERM</literal>
to tell subordinate server processes to quit normally and
<literal>SIGQUIT</literal> to terminate without the normal cleanup.
These signals <emphasis>should not</emphasis> be used by users. It
The <command>postgres</command> server uses <literal>SIGQUIT</literal>
to tell subordinate server processes to terminate without normal
cleanup.
This signal <emphasis>should not</emphasis> be used by users. It
is also unwise to send <literal>SIGKILL</literal> to a server
process &mdash; the main <command>postgres</command> process will
interpret this as a crash and will force all the sibling processes