Re: doc: clarify "pg_signal_backend" default role - Mailing list pgsql-hackers

From Tom Lane
Subject Re: doc: clarify "pg_signal_backend" default role
Date
Msg-id 3895.1566943493@sss.pgh.pa.us
Whole thread Raw
In response to doc: clarify "pg_signal_backend" default role  (Ian Barwick <ian.barwick@2ndquadrant.com>)
Responses Re: doc: clarify "pg_signal_backend" default role  (Ian Barwick <ian.barwick@2ndquadrant.com>)
Re: doc: clarify "pg_signal_backend" default role  (Ian Barwick <ian.barwick@2ndquadrant.com>)
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: a.kondratov@postgrespro.ru
Date:
Subject: Re: row filtering for logical replication
Next
From: Merlin Moncure
Date:
Subject: Re: pg11.5: ExecHashJoinNewBatch: glibc detected...double free orcorruption (!prev)