Re: doc: clarify "pg_signal_backend" default role

2019-08-27 Thread Ian Barwick
On 8/28/19 7:04 AM, Tom Lane wrote: Ian Barwick 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

Re: doc: clarify "pg_signal_backend" default role

2019-08-27 Thread Tom Lane
Ian Barwick 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. > At

Re: doc: clarify "pg_signal_backend" default role

2019-06-09 Thread Michael Paquier
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,

doc: clarify "pg_signal_backend" default role

2019-06-09 Thread Ian Barwick
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