Re: doc: clarify "pg_signal_backend" default role

Ian Barwick <ian.barwick@2ndquadrant.com>

From: Ian Barwick <ian.barwick@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, pgsql-docs <pgsql-docs@postgresql.org>
Date: 2019-08-28T01:13:38Z
Lists: pgsql-hackers, pgsql-docs
On 8/28/19 7:04 AM, Tom Lane wrote:
> 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.

Thanks!

> (Note: patches are less likely to fall through the cracks if you
> add them to the commitfest page.)

Yup, though I was intending to add that one together with a couple of
related minor doc patches to the next CF.

Regards

Ian Barwick

-- 
  Ian Barwick                   https://www.2ndQuadrant.com/
  PostgreSQL Development, 24x7 Support, Training & Services



Commits

  1. Doc: improve documentation of pg_signal_backend default role.