From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ian Barwick <ian.barwick@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: doc: clarify "pg_signal_backend" default role
Date: Tue, 27 Aug 2019 18:04:53 -0400
Message-ID: <3895.1566943493@sss.pgh.pa.us> (raw)
In-Reply-To: <89907e32-76f3-7282-a89c-ea19c722fe5d@2ndquadrant.com>
References: <89907e32-76f3-7282-a89c-ea19c722fe5d@2ndquadrant.com>
Ian Barwick <ian.barwick@2ndquadrant.com> writes:
> Currently the documentation for the default role "pg_signal_backend" states,
> somewhat ambiguously, "Send signals to other backends (eg: cancel query, terminate)",
> giving the impression other signals (e.g. SIGHUP) can be sent too, which is
> currently not the case.
> Attached patch clarifies this, adds a descriptive paragraph (similar to what
> the other default roles have) and a link to the "Server Signaling Functions"
> section.
Pushed with minor tweaking.
(Note: patches are less likely to fall through the cracks if you
add them to the commitfest page.)
regards, tom lane
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: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, ian.barwick@2ndquadrant.com, pgsql-hackers@postgresql.org
Subject: Re: doc: clarify "pg_signal_backend" default role
In-Reply-To: <3895.1566943493@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox