| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ian Barwick <ian(dot)barwick(at)2ndquadrant(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: doc: clarify "pg_signal_backend" default role |
| Date: | 2019-08-27 22:04:53 |
| Message-ID: | 3895.1566943493@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
Ian Barwick <ian(dot)barwick(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Barwick | 2019-08-28 01:13:38 | Re: doc: clarify "pg_signal_backend" default role |
| Previous Message | PG Doc comments form | 2019-08-27 08:55:29 | Truncate statement-level trigger behaviour |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2019-08-27 22:18:56 | Re: pg11.5: ExecHashJoinNewBatch: glibc detected...double free or corruption (!prev) |
| Previous Message | a.kondratov | 2019-08-27 21:10:47 | Re: row filtering for logical replication |