Subject: Re: doc: clarify "pg_signal_backend" default role
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>,
 pgsql-docs <pgsql-docs@postgresql.org>
References: <89907e32-76f3-7282-a89c-ea19c722fe5d@2ndquadrant.com>
 <3895.1566943493@sss.pgh.pa.us>
From: Ian Barwick <ian.barwick@2ndquadrant.com>
Message-ID: <8e8c064b-b421-fca0-5a76-0f0bcdb9952e@2ndquadrant.com>
Date: Wed, 28 Aug 2019 10:13:38 +0900
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <3895.1566943493@sss.pgh.pa.us>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

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