Re: doc: clarify "pg_signal_backend" default role

From: Ian Barwick <ian(dot)barwick(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: doc: clarify "pg_signal_backend" default role
Date: 2019-08-28 01:13:38
Message-ID: 8e8c064b-b421-fca0-5a76-0f0bcdb9952e@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

On 8/28/19 7:04 AM, Tom Lane wrote:
> Ian Barwick <ian(dot)barwick(at)2ndquadrant(dot)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

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2019-08-28 16:22:38 Most-common value docs in PG 12
Previous Message Tom Lane 2019-08-27 22:04:53 Re: doc: clarify "pg_signal_backend" default role

Browse pgsql-hackers by date

  From Date Subject
Next Message Ian Barwick 2019-08-28 01:57:24 Re: [PATCH] Make configuration file "include" directive handling more robust
Previous Message Jaime Casanova 2019-08-28 00:56:27 Re: PostgreSQL and Real Application Testing (RAT)