codekingpro/portable-devtools

1<?xml version="1.0" encoding="UTF-8" standalone="no"?>2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.5. Predefined Roles</title><link rel="stylesheet" type="text/css" href="stylesheet.css" /><link rev="made" href="pgsql-docs@lists.postgresql.org" /><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot" /><link rel="prev" href="role-removal.html" title="22.4. Dropping Roles" /><link rel="next" href="perm-functions.html" title="22.6. Function Security" /></head><body id="docContent" class="container-fluid col-10"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="5" align="center">22.5. Predefined Roles</th></tr><tr><td width="10%" align="left"><a accesskey="p" href="role-removal.html" title="22.4. Dropping Roles">Prev</a> </td><td width="10%" align="left"><a accesskey="u" href="user-manag.html" title="Chapter 22. Database Roles">Up</a></td><th width="60%" align="center">Chapter 22. Database Roles</th><td width="10%" align="right"><a accesskey="h" href="index.html" title="PostgreSQL 16.3 Documentation">Home</a></td><td width="10%" align="right"> <a accesskey="n" href="perm-functions.html" title="22.6. Function Security">Next</a></td></tr></table><hr /></div><div class="sect1" id="PREDEFINED-ROLES"><div class="titlepage"><div><div><h2 class="title" style="clear: both">22.5. Predefined Roles <a href="#PREDEFINED-ROLES" class="id_link">#</a></h2></div></div></div><a id="id-1.6.9.9.2" class="indexterm"></a><p>3   <span class="productname">PostgreSQL</span> provides a set of predefined roles4   that provide access to certain, commonly needed, privileged capabilities5   and information.  Administrators (including roles that have the6   <code class="literal">CREATEROLE</code> privilege) can <code class="command">GRANT</code> these7   roles to users and/or other roles in their environment, providing those8   users with access to the specified capabilities and information.9  </p><p>10   The predefined roles are described in <a class="xref" href="predefined-roles.html#PREDEFINED-ROLES-TABLE" title="Table 22.1. Predefined Roles">Table 22.1</a>.11   Note that the specific permissions for each of the roles may change in12   the future as additional capabilities are added.  Administrators13   should monitor the release notes for changes.14  </p><div class="table" id="PREDEFINED-ROLES-TABLE"><p class="title"><strong>Table 22.1. Predefined Roles</strong></p><div class="table-contents"><table class="table" summary="Predefined Roles" border="1"><colgroup><col class="col1" /><col class="col2" /></colgroup><thead><tr><th>Role</th><th>Allowed Access</th></tr></thead><tbody><tr><td>pg_read_all_data</td><td>Read all data (tables, views, sequences), as if having15       <code class="command">SELECT</code> rights on those objects, and USAGE rights on16       all schemas, even without having it explicitly.  This role does not have17       the role attribute <code class="literal">BYPASSRLS</code> set.  If RLS is being18       used, an administrator may wish to set <code class="literal">BYPASSRLS</code> on19       roles which this role is GRANTed to.</td></tr><tr><td>pg_write_all_data</td><td>Write all data (tables, views, sequences), as if having20       <code class="command">INSERT</code>, <code class="command">UPDATE</code>, and21       <code class="command">DELETE</code> rights on those objects, and USAGE rights on22       all schemas, even without having it explicitly.  This role does not have23       the role attribute <code class="literal">BYPASSRLS</code> set.  If RLS is being24       used, an administrator may wish to set <code class="literal">BYPASSRLS</code> on25       roles which this role is GRANTed to.</td></tr><tr><td>pg_read_all_settings</td><td>Read all configuration variables, even those normally visible only to26       superusers.</td></tr><tr><td>pg_read_all_stats</td><td>Read all pg_stat_* views and use various statistics related extensions,27       even those normally visible only to superusers.</td></tr><tr><td>pg_stat_scan_tables</td><td>Execute monitoring functions that may take <code class="literal">ACCESS SHARE</code> locks on tables,28       potentially for a long time.</td></tr><tr><td>pg_monitor</td><td>Read/execute various monitoring views and functions.29       This role is a member of <code class="literal">pg_read_all_settings</code>,30       <code class="literal">pg_read_all_stats</code> and31       <code class="literal">pg_stat_scan_tables</code>.</td></tr><tr><td>pg_database_owner</td><td>None.  Membership consists, implicitly, of the current database owner.</td></tr><tr><td>pg_signal_backend</td><td>Signal another backend to cancel a query or terminate its session.</td></tr><tr><td>pg_read_server_files</td><td>Allow reading files from any location the database can access on the server with COPY and32       other file-access functions.</td></tr><tr><td>pg_write_server_files</td><td>Allow writing to files in any location the database can access on the server with COPY and33       other file-access functions.</td></tr><tr><td>pg_execute_server_program</td><td>Allow executing programs on the database server as the user the database runs as with34       COPY and other functions which allow executing a server-side program.</td></tr><tr><td>pg_checkpoint</td><td>Allow executing35       the <a class="link" href="sql-checkpoint.html" title="CHECKPOINT"><code class="command">CHECKPOINT</code></a>36       command.</td></tr><tr><td>pg_use_reserved_connections</td><td>Allow use of connection slots reserved via37       <a class="xref" href="runtime-config-connection.html#GUC-RESERVED-CONNECTIONS">reserved_connections</a>.</td></tr><tr><td>pg_create_subscription</td><td>Allow users with <code class="literal">CREATE</code> permission on the38       database to issue39       <a class="link" href="sql-createsubscription.html" title="CREATE SUBSCRIPTION"><code class="command">CREATE SUBSCRIPTION</code></a>.</td></tr></tbody></table></div></div><br class="table-break" /><p>40  The <code class="literal">pg_monitor</code>, <code class="literal">pg_read_all_settings</code>,41  <code class="literal">pg_read_all_stats</code> and <code class="literal">pg_stat_scan_tables</code>42  roles are intended to allow administrators to easily configure a role for the43  purpose of monitoring the database server. They grant a set of common privileges44  allowing the role to read various useful configuration settings, statistics and45  other system information normally restricted to superusers.46  </p><p>47  The <code class="literal">pg_database_owner</code> role has one implicit,48  situation-dependent member, namely the owner of the current database.  Like49  any role, it can own objects or receive grants of access privileges.50  Consequently, once <code class="literal">pg_database_owner</code> has rights within a51  template database, each owner of a database instantiated from that template52  will exercise those rights.  <code class="literal">pg_database_owner</code> cannot be53  a member of any role, and it cannot have non-implicit members.  Initially,54  this role owns the <code class="literal">public</code> schema, so each database owner55  governs local use of the schema.56  </p><p>57  The <code class="literal">pg_signal_backend</code> role is intended to allow58  administrators to enable trusted, but non-superuser, roles to send signals59  to other backends. Currently this role enables sending of signals for60  canceling a query on another backend or terminating its session. A user61  granted this role cannot however send signals to a backend owned by a62  superuser.  See <a class="xref" href="functions-admin.html#FUNCTIONS-ADMIN-SIGNAL" title="9.27.2. Server Signaling Functions">Section 9.27.2</a>.63  </p><p>64  The <code class="literal">pg_read_server_files</code>, <code class="literal">pg_write_server_files</code> and65  <code class="literal">pg_execute_server_program</code> roles are intended to allow administrators to have66  trusted, but non-superuser, roles which are able to access files and run programs on the67  database server as the user the database runs as.  As these roles are able to access any file on68  the server file system, they bypass all database-level permission checks when accessing files69  directly and they could be used to gain superuser-level access, therefore70  great care should be taken when granting these roles to users.71  </p><p>72  Care should be taken when granting these roles to ensure they are only used where73  needed and with the understanding that these roles grant access to privileged74  information.75  </p><p>76   Administrators can grant access to these roles to users using the77   <a class="link" href="sql-grant.html" title="GRANT"><code class="command">GRANT</code></a> command, for example:78 79</p><pre class="programlisting">80GRANT pg_signal_backend TO admin_user;81</pre><p>82  </p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="role-removal.html" title="22.4. Dropping Roles">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="user-manag.html" title="Chapter 22. Database Roles">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="perm-functions.html" title="22.6. Function Security">Next</a></td></tr><tr><td width="40%" align="left" valign="top">22.4. Dropping Roles </td><td width="20%" align="center"><a accesskey="h" href="index.html" title="PostgreSQL 16.3 Documentation">Home</a></td><td width="40%" align="right" valign="top"> 22.6. Function Security</td></tr></table></div></body></html>