<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vertica Documentation – Privileges and access functions</title>
    <link>/en/sql-reference/functions/management-functions/privileges-and-access-functions/</link>
    <description>Recent content in Privileges and access functions on Vertica Documentation</description>
    <generator>Hugo -- gohugo.io</generator>
    
	  <atom:link href="/en/sql-reference/functions/management-functions/privileges-and-access-functions/index.xml" rel="self" type="application/rss+xml" />
    
    
      
        
      
    
    
    <item>
      <title>Sql-Reference: ENABLED_ROLE</title>
      <link>/en/sql-reference/functions/management-functions/privileges-and-access-functions/enabled-role/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/sql-reference/functions/management-functions/privileges-and-access-functions/enabled-role/</guid>
      <description>
        
        
        &lt;p&gt;Checks whether a Vertica &lt;a href=&#34;../../../../../en/admin/db-users-and-privileges/db-roles/&#34;&gt;user role&lt;/a&gt; is enabled, and returns true or false. This function is typically used when you create access policies on database roles.&lt;/p&gt;
&lt;p&gt;This is a meta-function. You must call meta-functions in a top-level &lt;a href=&#34;../../../../../en/sql-reference/statements/select/&#34;&gt;SELECT&lt;/a&gt; statement.&lt;/p&gt;

&lt;h2 id=&#34;behavior-type&#34;&gt;Behavior type&lt;/h2&gt;
&lt;a class=&#34;glosslink&#34; href=&#34;../../../../../en/glossary/volatile-functions/&#34; title=&#34;&#34;&gt;Volatile&lt;/a&gt;
&lt;h2 id=&#34;syntax&#34;&gt;Syntax&lt;/h2&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;ENABLED_ROLE ( &amp;#39;&lt;span class=&#34;code-variable&#34;&gt;role&lt;/span&gt;&amp;#39; )
&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;parameters&#34;&gt;Parameters&lt;/h2&gt;
&lt;dl&gt;
&lt;dt&gt;&lt;em&gt;&lt;code&gt;role&lt;/code&gt;&lt;/em&gt;&lt;/dt&gt;
&lt;dd&gt;The role to evaluate.&lt;/dd&gt;
&lt;/dl&gt;
&lt;h2 id=&#34;privileges&#34;&gt;Privileges&lt;/h2&gt;
&lt;p&gt;None&lt;/p&gt;
&lt;h2 id=&#34;examples&#34;&gt;Examples&lt;/h2&gt;
&lt;p&gt;See:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;a href=&#34;../../../../../en/admin/db-users-and-privileges/access-policies/creating-column-access-policies/&#34;&gt;Creating column access policies&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&#34;../../../../../en/admin/db-users-and-privileges/access-policies/creating-row-access-policies/&#34;&gt;Creating row access policies&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;see-also&#34;&gt;See also&lt;/h2&gt;
&lt;a href=&#34;../../../../../en/sql-reference/statements/create-statements/create-access-policy/&#34;&gt;CREATE ACCESS POLICY&lt;/a&gt;

      </description>
    </item>
    
    <item>
      <title>Sql-Reference: GET_PRIVILEGES_DESCRIPTION</title>
      <link>/en/sql-reference/functions/management-functions/privileges-and-access-functions/get-privileges-description/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/sql-reference/functions/management-functions/privileges-and-access-functions/get-privileges-description/</guid>
      <description>
        
        
        &lt;p&gt;Returns the effective privileges the current user has on an object, including explicit, &lt;a href=&#34;../../../../../en/admin/db-users-and-privileges/db-privileges/ownership-and-implicit-privileges/&#34;&gt;implicit&lt;/a&gt;, &lt;a href=&#34;../../../../../en/admin/db-users-and-privileges/db-privileges/inherited-privileges/&#34;&gt;inherited&lt;/a&gt;, and &lt;a href=&#34;../../../../../en/admin/db-users-and-privileges/db-roles/granting-privileges-to-roles/&#34;&gt;role-based&lt;/a&gt; privileges.&lt;/p&gt;
&lt;p&gt;Because this meta-function only returns &lt;a href=&#34;../../../../../en/admin/db-users-and-privileges/db-privileges/effective-privileges/&#34;&gt;effective privileges&lt;/a&gt;, GET_PRIVILEGES_DESCRIPTION only returns privileges with fully-satisfied prerequisites. For a list of prerequisites for common operations, see &lt;a href=&#34;../../../../../en/admin/db-users-and-privileges/db-privileges/privileges-required-common-db-operations/&#34;&gt;Privileges required for common database operations&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;For example, a user must have the following privileges to query a table:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Schema: USAGE&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Table: SELECT&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If user Brooke has SELECT privileges on table &lt;code&gt;s1.t1&lt;/code&gt; but lacks USAGE privileges on schema &lt;code&gt;s1&lt;/code&gt;, Brooke cannot query the table, and GET_PRIVILEGES_DESCRIPTION does not return SELECT as a privilege for the table.&lt;/p&gt;

&lt;div class=&#34;alert admonition note&#34; role=&#34;alert&#34;&gt;
&lt;h4 class=&#34;admonition-head&#34;&gt;Note&lt;/h4&gt;

Inherited privileges are not displayed if privilege inheritance is disabled at the database level.

&lt;/div&gt;

&lt;p&gt;This is a meta-function. You must call meta-functions in a top-level &lt;a href=&#34;../../../../../en/sql-reference/statements/select/&#34;&gt;SELECT&lt;/a&gt; statement.&lt;/p&gt;

&lt;h2 id=&#34;behavior-type&#34;&gt;Behavior type&lt;/h2&gt;
&lt;a class=&#34;glosslink&#34; href=&#34;../../../../../en/glossary/volatile-functions/&#34; title=&#34;&#34;&gt;Volatile&lt;/a&gt;
&lt;h2 id=&#34;syntax&#34;&gt;Syntax&lt;/h2&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;GET_PRIVILEGES_DESCRIPTION( &amp;#39;&lt;span class=&#34;code-variable&#34;&gt;type&lt;/span&gt;&amp;#39;, &amp;#39;[[&lt;span class=&#34;code-variable&#34;&gt;database&lt;/span&gt;.]&lt;span class=&#34;code-variable&#34;&gt;schema.&lt;/span&gt;]&lt;span class=&#34;code-variable&#34;&gt;name&lt;/span&gt;&amp;#39; );
&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;parameters&#34;&gt;Parameters&lt;/h2&gt;
&lt;dl&gt;
&lt;dt&gt;&lt;em&gt;&lt;code&gt;type&lt;/code&gt;&lt;/em&gt;&lt;/dt&gt;
&lt;dd&gt;Specifies an object type, one of the following:
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;database&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;table&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;schema&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;view&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;sequence&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;model&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;library&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;resource pool&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/dd&gt;
&lt;dt&gt;&lt;code&gt;[&lt;/code&gt;&lt;em&gt;&lt;code&gt;database&lt;/code&gt;&lt;/em&gt;&lt;code&gt;.]&lt;/code&gt;&lt;em&gt;&lt;code&gt;schema&lt;/code&gt;&lt;/em&gt;&lt;/dt&gt;
&lt;dd&gt;Specifies a database and schema, by default the current database and &lt;code&gt;public&lt;/code&gt;, respectively.&lt;/dd&gt;
&lt;dt&gt;&lt;em&gt;&lt;code&gt;name&lt;/code&gt;&lt;/em&gt;&lt;/dt&gt;
&lt;dd&gt;Name of the target object&lt;/dd&gt;
&lt;/dl&gt;
&lt;h2 id=&#34;privileges&#34;&gt;Privileges&lt;/h2&gt;
&lt;p&gt;None&lt;/p&gt;
&lt;h2 id=&#34;examples&#34;&gt;Examples&lt;/h2&gt;
&lt;p&gt;In the following example, user Glenn has set the REPORTER role and wants to check his effective privileges on schema &lt;code&gt;s1&lt;/code&gt; and table &lt;code&gt;s1.articles&lt;/code&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Table &lt;code&gt;s1.articles&lt;/code&gt; inherits privileges from its schema (&lt;code&gt;s1&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The REPORTER role has the following privileges:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;SELECT on schema &lt;code&gt;s1&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;INSERT WITH GRANT OPTION on table &lt;code&gt;s1.articles&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;User Glenn has the following privileges:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;UPDATE and USAGE on schema &lt;code&gt;s1&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;DELETE on table &lt;code&gt;s1.articles&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;GET_PRIVILEGES_DESCRIPTION returns the following effective privileges for Glenn on schema &lt;code&gt;s1&lt;/code&gt;:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;=&amp;gt; SELECT GET_PRIVILEGES_DESCRIPTION(&amp;#39;schema&amp;#39;, &amp;#39;s1&amp;#39;);
   GET_PRIVILEGES_DESCRIPTION
--------------------------------
 SELECT, UPDATE, USAGE
(1 row)
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;GET_PRIVILEGES_DESCRIPTION returns the following effective privileges for Glenn on table &lt;code&gt;s1.articles&lt;/code&gt;:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;
=&amp;gt; SELECT GET_PRIVILEGES_DESCRIPTION(&amp;#39;table&amp;#39;, &amp;#39;s1.articles&amp;#39;);
   GET_PRIVILEGES_DESCRIPTION
--------------------------------
 INSERT*, SELECT, UPDATE, DELETE
(1 row)
&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id=&#34;see-also&#34;&gt;See also&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;a href=&#34;../../../../../en/admin/db-users-and-privileges/&#34;&gt;Database users and privileges&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&#34;../../../../../en/admin/db-users-and-privileges/db-roles/&#34;&gt;Database roles&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&#34;../../../../../en/admin/db-users-and-privileges/db-privileges/granting-and-revoking-privileges/&#34;&gt;Granting and revoking privileges&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Sql-Reference: HAS_ROLE</title>
      <link>/en/sql-reference/functions/management-functions/privileges-and-access-functions/has-role/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/sql-reference/functions/management-functions/privileges-and-access-functions/has-role/</guid>
      <description>
        
        
        &lt;p&gt;Checks whether a Vertica &lt;a href=&#34;../../../../../en/admin/db-users-and-privileges/db-roles/&#34;&gt;user role&lt;/a&gt; is granted to the specified user or role, and returns true or false.&lt;/p&gt;
&lt;p&gt;You can also query system tables &lt;a href=&#34;../../../../../en/sql-reference/system-tables/v-catalog-schema/roles/&#34;&gt;ROLES&lt;/a&gt;, &lt;a href=&#34;../../../../../en/sql-reference/system-tables/v-catalog-schema/grants/&#34;&gt;GRANTS&lt;/a&gt;, and &lt;a href=&#34;../../../../../en/sql-reference/system-tables/v-catalog-schema/users/&#34;&gt;USERS&lt;/a&gt; to obtain information on users and their role assignments. For details, see &lt;a href=&#34;../../../../../en/admin/db-users-and-privileges/db-roles/viewing-user-roles/&#34;&gt;Viewing user roles&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This is a meta-function. You must call meta-functions in a top-level &lt;a href=&#34;../../../../../en/sql-reference/statements/select/&#34;&gt;SELECT&lt;/a&gt; statement.&lt;/p&gt;

&lt;h2 id=&#34;behavior-type&#34;&gt;Behavior type&lt;/h2&gt;
&lt;a class=&#34;glosslink&#34; href=&#34;../../../../../en/glossary/stable-functions/&#34; title=&#34;See also Immutable (invariant) functions.&#34;&gt;Stable&lt;/a&gt;
&lt;h2 id=&#34;syntax&#34;&gt;Syntax&lt;/h2&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;HAS_ROLE( [ &amp;#39;&lt;span class=&#34;code-variable&#34;&gt;grantee&lt;/span&gt;&amp;#39; ,] &amp;#39;&lt;span class=&#34;code-variable&#34;&gt;verify‑role&lt;/span&gt;&amp;#39; );
&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;parameters&#34;&gt;Parameters&lt;/h2&gt;
&lt;dl&gt;
&lt;dt&gt;&lt;em&gt;&lt;code&gt;grantee&lt;/code&gt;&lt;/em&gt;&lt;/dt&gt;
&lt;dd&gt;Valid only for superusers, specifies the name of a user or role to look up. If this argument is omitted, the function uses the current user name (
&lt;code&gt;&lt;a href=&#34;../../../../../en/sql-reference/functions/system-information-functions/current-user/&#34;&gt;CURRENT_USER&lt;/a&gt;&lt;/code&gt;). If you specify a role, Vertica checks whether this role is granted to the role specified in &lt;em&gt;&lt;code&gt;verify‑role&lt;/code&gt;&lt;/em&gt;.

&lt;div class=&#34;admonition important&#34; role=&#34;alert&#34;&gt;
&lt;h4 class=&#34;admonition-head&#34;&gt;Important&lt;/h4&gt;
If a non-superuser supplies this argument, Vertica returns an error.
&lt;/div&gt;&lt;/dd&gt;
&lt;dt&gt;&lt;em&gt;&lt;code&gt;verify‑role&lt;/code&gt;&lt;/em&gt;&lt;/dt&gt;
&lt;dd&gt;Name of the role to verify for &lt;em&gt;&lt;code&gt;grantee&lt;/code&gt;&lt;/em&gt;.&lt;/dd&gt;
&lt;/dl&gt;
&lt;h2 id=&#34;privileges&#34;&gt;Privileges&lt;/h2&gt;
&lt;p&gt;None&lt;/p&gt;
&lt;h2 id=&#34;examples&#34;&gt;Examples&lt;/h2&gt;
&lt;p&gt;In the following example, a &lt;code&gt;dbadmin&lt;/code&gt; user checks whether user &lt;code&gt;MikeL&lt;/code&gt; is assigned the &lt;code&gt;admnistrator&lt;/code&gt; role:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;=&amp;gt; \c
You are now connected as user &amp;#34;dbadmin&amp;#34;.
=&amp;gt; SELECT HAS_ROLE(&amp;#39;MikeL&amp;#39;, &amp;#39;administrator&amp;#39;);
 HAS_ROLE
----------
 t
(1 row)
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;User &lt;code&gt;MikeL&lt;/code&gt; checks whether he has the &lt;code&gt;regional_manager&lt;/code&gt; role:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;=&amp;gt; \c - MikeL
You are now connected as user &amp;#34;MikeL&amp;#34;.
=&amp;gt; SELECT HAS_ROLE(&amp;#39;regional_manager&amp;#39;);
 HAS_ROLE
----------
 f
(1 row)
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;The dbadmin grants the &lt;code&gt;regional_manager&lt;/code&gt; role to the &lt;code&gt;administrator&lt;/code&gt; role. On checking again, &lt;code&gt;MikeL&lt;/code&gt; verifies that he now has the &lt;code&gt;regional_manager&lt;/code&gt; role:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;dbadmin=&amp;gt; \c
You are now connected as user &amp;#34;dbadmin&amp;#34;.
dbadmin=&amp;gt; GRANT regional_manager to administrator;
GRANT ROLE
dbadmin=&amp;gt; \c - MikeL
You are now connected as user &amp;#34;MikeL&amp;#34;.
dbadmin=&amp;gt; SELECT HAS_ROLE(&amp;#39;regional_manager&amp;#39;);
 HAS_ROLE
----------
 t
(1 row)
&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id=&#34;see-also&#34;&gt;See also&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;a href=&#34;../../../../../en/sql-reference/system-tables/v-catalog-schema/grants/&#34;&gt;GRANTS&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&#34;../../../../../en/sql-reference/system-tables/v-catalog-schema/roles/&#34;&gt;ROLES&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&#34;../../../../../en/sql-reference/system-tables/v-catalog-schema/users/&#34;&gt;USERS&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&#34;../../../../../en/admin/db-users-and-privileges/&#34;&gt;Database users and privileges&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Sql-Reference: RELEASE_SYSTEM_TABLES_ACCESS</title>
      <link>/en/sql-reference/functions/management-functions/privileges-and-access-functions/release-system-tables-access/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/sql-reference/functions/management-functions/privileges-and-access-functions/release-system-tables-access/</guid>
      <description>
        
        
        &lt;p&gt;Enables non-superuser access to all system tables. After you call this function, Vertica ignores the IS_ACCESSIBLE_DURING_LOCKDOWN setting in table &lt;a href=&#34;../../../../../en/sql-reference/system-tables/v-catalog-schema/system-tables/&#34;&gt;SYSTEM_TABLES&lt;/a&gt;. To resume enforcement of access restrictions on non-superusers to system tables, call &lt;a href=&#34;../../../../../en/sql-reference/functions/management-functions/privileges-and-access-functions/restrict-system-tables-access/&#34;&gt;RESTRICT_SYSTEM_TABLES_ACCESS&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This is a meta-function. You must call meta-functions in a top-level &lt;a href=&#34;../../../../../en/sql-reference/statements/select/&#34;&gt;SELECT&lt;/a&gt; statement.&lt;/p&gt;

&lt;h2 id=&#34;behavior-type&#34;&gt;Behavior type&lt;/h2&gt;
&lt;a class=&#34;glosslink&#34; href=&#34;../../../../../en/glossary/volatile-functions/&#34; title=&#34;&#34;&gt;Volatile&lt;/a&gt;
&lt;h2 id=&#34;syntax&#34;&gt;Syntax&lt;/h2&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;RELEASE_SYSTEM_TABLES_ACCESS()
&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;privileges&#34;&gt;Privileges&lt;/h2&gt;
&lt;p&gt;Superuser&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Sql-Reference: RESTRICT_SYSTEM_TABLES_ACCESS</title>
      <link>/en/sql-reference/functions/management-functions/privileges-and-access-functions/restrict-system-tables-access/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/sql-reference/functions/management-functions/privileges-and-access-functions/restrict-system-tables-access/</guid>
      <description>
        
        
        &lt;p&gt;Checks system table &lt;a href=&#34;../../../../../en/sql-reference/system-tables/v-catalog-schema/system-tables/&#34;&gt;SYSTEM_TABLES&lt;/a&gt; to determine which system tables non-superusers can access. Non-superuser access to each system table is specified by the Boolean column IS_ACCESSIBLE_DURING_LOCKDOWN. When you call this function, Vertica checks the IS_ACCESSIBLE_DURING_LOCKDOWN setting on each system table, and enforces access on all non-superuser accordingly.&lt;/p&gt;
&lt;p&gt;By default, Vertica enforces IS_ACCESSIBLE_DURING_LOCKDOWN settings. To enable non-superuser access to all system tables, you must explicitly call &lt;a href=&#34;../../../../../en/sql-reference/functions/management-functions/privileges-and-access-functions/release-system-tables-access/&#34;&gt;RELEASE_SYSTEM_TABLES_ACCESS&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This is a meta-function. You must call meta-functions in a top-level &lt;a href=&#34;../../../../../en/sql-reference/statements/select/&#34;&gt;SELECT&lt;/a&gt; statement.&lt;/p&gt;

&lt;h2 id=&#34;behavior-type&#34;&gt;Behavior type&lt;/h2&gt;
&lt;a class=&#34;glosslink&#34; href=&#34;../../../../../en/glossary/volatile-functions/&#34; title=&#34;&#34;&gt;Volatile&lt;/a&gt;
&lt;h2 id=&#34;syntax&#34;&gt;Syntax&lt;/h2&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;RESTRICT_SYSTEM_TABLES_ACCESS()
&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;privileges&#34;&gt;Privileges&lt;/h2&gt;
&lt;p&gt;Superuser&lt;/p&gt;

      </description>
    </item>
    
  </channel>
</rss>
