| From: | Ian Barwick <ian(dot)barwick(at)2ndquadrant(dot)com> |
|---|---|
| To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | doc: clarify "pg_signal_backend" default role |
| Date: | 2019-06-10 02:06:54 |
| Message-ID: | 89907e32-76f3-7282-a89c-ea19c722fe5d@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
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
| Attachment | Content-Type | Size |
|---|---|---|
| doc-pg_signal_backend.patch | text/x-patch | 1.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-06-10 05:35:58 | Re: doc: clarify "pg_signal_backend" default role |
| Previous Message | Tom Lane | 2019-06-09 14:55:16 | Re: Unexplained createdb mydb response |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-06-10 02:12:46 | Re: [PATCH] Fix potential memoryleak in guc.c |
| Previous Message | Zhang, Jie | 2019-06-10 01:58:48 | [PATCH] Fix potential memoryleak in guc.c |