public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Josh Kupershmidt <[email protected]>
Cc: pgsql-docs <[email protected]>
Subject: Re: Out of date advice about SIGTERM'ing backends
Date: Thu, 30 Aug 2012 17:58:48 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAK3UJRHHVHSLewwwXzKcvhKoXagxR07j=2U4P9hGqPmA=oJ1Kg@mail.gmail.com>
References: <CAK3UJRHHVHSLewwwXzKcvhKoXagxR07j=2U4P9hGqPmA=oJ1Kg@mail.gmail.com>
On Fri, Jun 29, 2012 at 08:10:40PM -0700, Josh Kupershmidt wrote:
> Hi all,
>
> In the "Notes" section[0] of the postgres command's page, this advice is given:
>
> | The postgres server uses SIGTERM to tell subordinate server
> | processes to quit normally and SIGQUIT to terminate without
> | the normal cleanup. These signals should not be used by users.
>
> I think now that we've added pg_terminate_backend() and made it
> callable by non-superusers, we should relax the caveat against using
> SIGTERM against backends. The warning to stay away from using SIGQUIT
> seems fine as-is. Patch attached.
Patch applied for 9.3.
---------------------------------------------------------------------------
>
> Josh
>
> [0] http://www.postgresql.org/docs/9.2/static/app-postgres.html#AEN87192
> diff --git a/doc/src/sgml/ref/postgres-ref.sgml b/doc/src/sgml/ref/postgres-ref.sgml
> new file mode 100644
> index 4e5cd02..a1d014d
> *** a/doc/src/sgml/ref/postgres-ref.sgml
> --- b/doc/src/sgml/ref/postgres-ref.sgml
> *************** PostgreSQL documentation
> *** 726,739 ****
>
> <para>
> To cancel a running query, send the <literal>SIGINT</literal> signal
> ! to the process running that command.
> </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
> 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
> --- 726,743 ----
>
> <para>
> To cancel a running query, send the <literal>SIGINT</literal> signal
> ! 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>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
>
> --
> Sent via pgsql-docs mailing list ([email protected])
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-docs
--
Bruce Momjian <[email protected]> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
view thread (2+ messages)
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], [email protected]
Subject: Re: Out of date advice about SIGTERM'ing backends
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