Horton

Thread

Commits

  1. Doc: improve documentation of pg_signal_backend default role.

  1. doc: clarify "pg_signal_backend" default role

    Ian Barwick <ian.barwick@2ndquadrant.com> — 2019-06-10T02:06:54Z

    Hi

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.

Patch applies cleanly to HEAD and REL_11_STABLE.


Regards

Ian Barwick


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

  2. Re: doc: clarify "pg_signal_backend" default role

    Michael Paquier <michael@paquier.xyz> — 2019-06-10T05:35:58Z

    On Mon, Jun 10, 2019 at 11:06:54AM +0900, Ian Barwick wrote:
> 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.

(Perhaps you should avoid cross-posting?)

OK, I can see your point.

> 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.

+1 for being more descriptive here.
--
Michael

  3. Re: doc: clarify "pg_signal_backend" default role

    Tom Lane <tgl@sss.pgh.pa.us> — 2019-08-27T22:04:53Z

    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

  4. Re: doc: clarify "pg_signal_backend" default role

    Ian Barwick <ian.barwick@2ndquadrant.com> — 2019-08-28T01:13:38Z

    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