Re: doc: clarify "pg_signal_backend" default role
| От | Tom Lane |
|---|---|
| Тема | Re: doc: clarify "pg_signal_backend" default role |
| Дата | |
| Msg-id | 3895.1566943493@sss.pgh.pa.us обсуждение |
| Ответ на | doc: clarify "pg_signal_backend" default role (Ian Barwick <ian.barwick@2ndquadrant.com>) |
| Ответы |
Re: doc: clarify "pg_signal_backend" default role
Re: doc: clarify "pg_signal_backend" default role |
| Список | 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 по дате отправления: