From b5dc7612a5f66a08c6d46656d359fc1c69670f36 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 30 Aug 2012 17:58:36 -0400
Subject: [PATCH] Properly document that SIGTERM is OK for users to use on a
postgres session, now that pg_terminate_backend() uses it.
Josh Kupershmidt
---
doc/src/sgml/ref/postgres-ref.sgml | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/ref/postgres-ref.sgml b/doc/src/sgml/ref/postgres-ref.sgml
index 41745fb34dc..943a3be00e3 100644
--- a/doc/src/sgml/ref/postgres-ref.sgml
+++ b/doc/src/sgml/ref/postgres-ref.sgml
@@ -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 — the main <command>postgres</command> process will
interpret this as a crash and will force all the sibling processes
--
GitLab