| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Ian Barwick <ian(dot)barwick(at)2ndquadrant(dot)com> |
| Cc: | pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: doc: clarify "pg_signal_backend" default role |
| Date: | 2019-06-10 05:35:58 |
| Message-ID: | 20190610053558.GD2199@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2019-06-11 11:19:32 | Add XSL stylesheet to fix up SVG files |
| Previous Message | Ian Barwick | 2019-06-10 02:06:54 | doc: clarify "pg_signal_backend" default role |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zhenghua Lyu | 2019-06-10 06:00:57 | Questions of 'for update' |
| Previous Message | Amit Khandekar | 2019-06-10 05:07:44 | Re: Minimal logical decoding on standbys |