Postgres Pro
Downloads
Home   >   mailing lists

doc: clarify "pg_signal_backend" default role - Mailing list pgsql-hackers

From Ian Barwick
Subject doc: clarify "pg_signal_backend" default role
Date
Msg-id 89907e32-76f3-7282-a89c-ea19c722fe5d@2ndquadrant.com
Whole thread Raw
Responses Re: doc: clarify "pg_signal_backend" default role  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: doc: clarify "pg_signal_backend" default role  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

Previous
From: "Zhang, Jie"
Date:
Subject: [PATCH] Fix potential memoryleak in guc.c
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] Fix potential memoryleak in guc.c