21.5. Default Roles
PostgreSQL provides a set of default roles which provide access to certain, commonly needed, privileged capabilities and information. Administrators can GRANT these roles to users and/or other roles in their environment, providing those users with access to the specified capabilities and information.
The default roles are described in Table 21.1. Note that the specific permissions for each of the default roles may change in the future as additional capabilities are added. Administrators should monitor the release notes for changes.
Table 21.1. Default Roles
|pg_read_all_settings||Read all configuration variables, even those normally visible only to superusers.|
|pg_read_all_stats||Read all pg_stat_* views and use various statistics related extensions, even those normally visible only to superusers.|
|pg_stat_scan_tables||Execute monitoring functions that may take |
|pg_monitor||Read/execute various monitoring views and functions.
This role is a member of |
|pg_signal_backend||Signal another backend to cancel a query or terminate its session.|
roles are intended to allow administrators to easily configure a role for the
purpose of monitoring the database server. They grant a set of common privileges
allowing the role to read various useful configuration settings, statistics and
other system information normally restricted to superusers.
pg_signal_backend role is intended to allow
administrators to enable trusted, but non-superuser, roles to send signals
to other backends. Currently this role enables sending of signals for
canceling a query on another backend or terminating its session. A user
granted this role cannot however send signals to a backend owned by a
superuser. See Section 9.26.2.
Care should be taken when granting these roles to ensure they are only used where needed to perform the desired monitoring.
Administrators can grant access to these roles to users using the GRANT command, for example:
GRANT pg_signal_backend TO admin_user;