What's New
Function Overview
Product Bulletin
- Product Notice
- Version Support Notes
Service Overview
- GaussDB(DWS) Infographics
- What Is GaussDB(DWS)?
- Data Warehouse Types
- Data Warehouse Flavors
- Advantages
- Application Scenarios
- Functions
- Concepts
- Related Services
- Security
- GaussDB(DWS) Permissions Management
- GaussDB(DWS) Access
- Restrictions
- Technical Support
- Service Quotas
- GaussDB(DWS) Technical Specifications
Billing
- GaussDB(DWS) Billing Overview
- Billing Modes
- Item
- Billing Examples
- Billing Mode Change
- Renewal
  - Overview
  - Manual Renewal
- Bills
- Arrears
- Stopping Billing
- Cost Management
- Billing FAQs
Getting Started
- Checkpoint Vehicle Analysis
- Supply Chain Requirement Analysis of a Company
- Operations Status Analysis of a Retail Department Store
- Creating a Time Series Table
- Best Practices of Hot and Cold Data Management
- Best Practices for Automatic Partition Management
- Creating a Cluster and Connecting to It
- Using CDM to Migrate MySQL Data to the GaussDB(DWS) Cluster
- Using DLI Flink Jobs to Write Kafka Data to GaussDB(DWS) in Real Time
- Basic SQL Operations
- Database Quick Start
- Getting Started with Common Practices
User Guide
- Using GaussDB(DWS)
- Preparations
- Creating a GaussDB(DWS) Cluster
- Connecting to a GaussDB(DWS) Cluster
- Creating a GaussDB(DWS) Database and User
- Migrating Service Data to a GaussDB(DWS) Cluster
  - Migrating Data to a GaussDB(DWS) Cluster Using GDS-Kafka
  - Data Source Management
- GaussDB(DWS) Cluster Data Security and Encryption
- GaussDB(DWS) Cluster Management
- GaussDB(DWS) Cluster O&M
Best Practices
- Import and Export
- Data Migration
- Data Analytics
- Decoupled Storage and Compute
  - DWS 3.0 Decoupled Storage and Compute Usage Suggestions and Performance Optimization
- Data Development
- Database Management
- Performance Tuning
  - Optimizing Table Structure Design to Enhance GaussDB(DWS) Query Performance
  - Analyzing SQL Statements That Are Being Executed to Handle GaussDB(DWS) Performance Issues
- Cluster Management
  - Binding Different Resource Pools to Two Types of Jobs to Balance Load for GaussDB(DWS)
  - Scaling Options for GaussDB(DWS) with a Coupled Storage-Compute Architecture
Data Migration and Synchronization
- Data Migration to GaussDB(DWS)
- Importing Data
- Full Database Migration
  - Using CDM to Migrate Data to GaussDB(DWS)
  - Using DSC to Migrate SQL Scripts
- Real-time Import
  - Using DRS to Import Data to GaussDB(DWS)
  - Real-time Data Import From Kafka GaussDB(DWS)
- Metadata Migration
  - Using gs_dump and gs_dumpall to Export Metadata
  - Using gs_restore to Import Data
- Exporting Data
- Other Operations
Developer Guide
- Standard data warehouse (9.1.0.x)
- Standard data warehouse (8.1.3.x)
- Hybrid Data Warehouse (9.1.0.x）
- Hybrid Data Warehouse (8.1.3.x）
- Historical Versions
SQL Syntax Reference
- SQL Syntax Reference (9.1.0.x)
- SQL Syntax Reference (8.1.3.x)
- Historical Versions
Performance Tuning
- Overview of Query Performance Optimization
- Query Execution Process
- SQL Execution Plan
- SQL Optimization Guide
- Optimization Cases
- SQL Execution Troubleshooting
- query_band Load Identification
- Common Performance Parameter Optimization Design
Tool Guide
- Overview
- Downloading Related Tools
- gsql
- Data Studio
- GDS
- DSC
- DataCheck
- DWS-Connector
- Server Tool
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
- API Description
- Application Cases
  - Using Postman to Call the API for Creating a Cluster
  - Using Postman to Call the API for Creating a Snapshot
- Introduction
- Appendix
SDK Reference
- SDK Overview
FAQs
- Top FAQs
- Product Consulting
- Database Connections
- Data Migration
- Database Usage
- Cluster Management
- Account Permissions
- Database Performance
- Backup and Restoration
  1. Why Does It Take a Long Time to Create an Automated Snapshot in GaussDB(DWS)?
  2. Does a GaussDB(DWS) Snapshot Have the Same Function as an EVS Snapshot?
Troubleshooting
- Database Connections
- JDBC/ODBC
- Data Import and Export
- Database Parameter Modification
- Account/Permission/Password
- Cluster Performance
- Cluster Exceptions
  - The Disk Usage Alarm Is Frequently Generated
- Database Use
Videos
Performance White Paper
- Overview
- Test Result
  - TPC-H Single Query Test
  - TPC-DS Single Query Test
- Test Methods
- Appendixes
  - TPC-H Test Sets
  - TPC-DS Test Sets
Technical White Paper
- GaussDB(DWS)
- Platforms and Technical Specifications Supported by GaussDB(DWS)
  - Technical Specifications
- GaussDB(DWS) Core Technologies
- GaussDB(DWS) Tools
  - Client Tools
  - Database Monitoring Tool
- External APIs
Error Code Reference
- 8.2.0 and earlier versions
  - Management Console Error Code
  - Data Warehouse Service Error Codes
- 8.2.1 or later versions
Glossary
More Documents
- User Guide
- API Reference (ME-Abu Dhabi Region)
- Developer Guide (ME-Abu Dhabi Region)
- SQL Syntax Reference (ME-Abu Dhabi Region)
- Tool Guide (ME-Abu Dhabi Region)
- Error Code Reference (ME-Abu Dhabi Region)
  - Management Console Error Code
- User Guide (Paris Region)
- API Reference (Paris Region)
- Developer Guide (Paris Region)
- SQL Syntax Reference (Paris Region)
- Tool Guide (Paris Region)
- Error Code Reference (Paris Region)
  - Management Console Error Code
- User Guide (Kuala Lumpur Region)
- API Reference (Kuala Lumpur Region)
- Developer Guide (Kuala Lumpur Region)
- SQL Syntax Reference (Kuala Lumpur Region)
- Tool Guide (Kuala Lumpur Region)
- Error Code Reference (Kuala Lumpur Region)
  - Management Console Error Code
General Reference
- Glossary
- Service Level Agreement
- White Papers
- Endpoints
- Permissions

On this page

has_any_column_privilege(user, table, privilege)
has_any_column_privilege(table, privilege)
has_column_privilege(user, table, column, privilege)
has_column_privilege(table, column, privilege)
has_database_privilege(user, database, privilege)
has_database_privilege(database, privilege)
has_foreign_data_wrapper_privilege(user, fdw, privilege)
has_foreign_data_wrapper_privilege(fdw, privilege)
has_function_privilege(user, function, privilege)
has_function_privilege(function, privilege)
has_language_privilege(user, language, privilege)
has_language_privilege(language, privilege)
has_schema_privilege(user, schema, privilege)
has_schema_privilege(schema, privilege)
has_server_privilege(user, server, privilege)
has_server_privilege(server, privilege)
has_table_privilege(user, table, privilege)
has_table_privilege(table, privilege)
pg_has_role(user, role, privilege)
pg_has_role(role, privilege)

Show all

Help Center/ GaussDB(DWS)/ SQL Syntax Reference/ SQL Syntax Reference (8.1.3.x)/ Functions and Operators/ System Information Functions/ Access Privilege Inquiry Functions

Access Privilege Inquiry Functions

Updated on 2024-09-03 GMT+08:00

View PDF

has_any_column_privilege(user, table, privilege)

Description: Queries whether a specified user has permission for any column of table.

Parameters: user can be declared by name (text type) or OID. table can be declared by name (text type) or OID. privilege is declared using a text string (text type). The text string can be SELECT, INSERT, UPDATE, REFERENCES, or multiple permission types separated by commas (,).

Return type: boolean

has_any_column_privilege(table, privilege)

Description: Queries whether the current user has permission for any column of table.

Parameters: table can be declared by name (text type) or OID. privilege is declared using a text string (text type). The text string can be SELECT, INSERT, UPDATE, REFERENCES, or multiple permission types separated by commas (,).

Return type: boolean

has_any_column_privilege checks whether a user can access any column of a table in a particular way. Its parameter possibilities are analogous to has_table_privilege, except that the desired access permission type must be some combination of SELECT, INSERT, UPDATE, or REFERENCES.

NOTE:

Note that having any of these permissions at the table level implicitly grants it for each column of the table, so has_any_column_privilege will always return true if has_table_privilege does for the same parameters. But has_any_column_privilege also succeeds if there is a column-level grant of the permission for at least one column.

has_column_privilege(user, table, column, privilege)

Description: Queries whether a specified user has permission for column.

Parameters: user can be declared by name (text type) or OID. table can be declared by name (text type) or OID. column can be declared by a column name (text type) or an attribute number (smallint type). privilege is declared using a text string. The text string can be SELECT, INSERT, UPDATE, REFERENCES, or multiple permission types separated by commas (,).

Return type: boolean

has_column_privilege(table, column, privilege)

Description: Queries whether the current user has permission for column.

Parameters: table can be declared by name (text type) or OID. column can be declared by a column name (text type) or an attribute number (smallint type). privilege is declared using a text string. The text string can be SELECT, INSERT, UPDATE, REFERENCES, or multiple permission types separated by commas (,).

Return type: boolean

has_column_privilege checks whether a user can access a column in a particular way. Its argument possibilities are analogous to has_table_privilege, with the addition that the column can be specified either by name or attribute number. The desired access permission type must evaluate to some combination of SELECT, INSERT, UPDATE, or REFERENCES.

NOTE:

Note that having any of these permissions at the table level implicitly grants it for each column of the table.

has_database_privilege(user, database, privilege)

Description: Queries whether a specified user has permission for database.

Parameters: user can be declared by name (text type) or OID. database can be declared by name (text type) or OID. privilege is declared using a text string. The text string can be SELECT, INSERT, UPDATE, REFERENCES, or multiple permission types separated by commas (,).

Return type: boolean

has_database_privilege(database, privilege)

Description: Queries whether the current user has permission for database.

Parameters: database can be declared by name (text type) or OID. privilege is declared using a text string. The text string can be CREATE, CONNECT, TEMPORARY, or TEMP, or multiple permission types separated by commas (,).

Return type: boolean

Note: has_database_privilege checks whether a user can access a database in a particular way. Its argument possibilities are analogous to has_table_privilege. The desired access permission type must evaluate to some combination of CREATE, CONNECT, TEMPORARY, or TEMP (which is equivalent to TEMPORARY).

has_foreign_data_wrapper_privilege(user, fdw, privilege)

Description: Queries whether a specified user has permission for foreign-data wrapper.

Parameters: user can be declared by name (text type) or OID. fdw indicates a foreign-data wrapper, which can be declared by name (text type) or OID. privilege is declared using a text string, which must be USAGE.

The fdw parameter indicates the name or ID of the foreign data wrapper.

Return type: boolean

has_foreign_data_wrapper_privilege(fdw, privilege)

Description: Queries whether the current user has permission for foreign-data wrapper.

Parameters: fdw indicates a foreign-data wrapper, which can be declared by name (text type) or OID. privilege is declared using a text string, which must be USAGE.

Return type: boolean

Note: has_foreign_data_wrapper_privilege checks whether a user can access a foreign-data wrapper in a particular way. Its argument possibilities are analogous to has_table_privilege. The desired access permission type must evaluate to USAGE.

has_function_privilege(user, function, privilege)

Description: Queries whether a specified user has permission for function.

Parameters: user can be declared by name (text type) or OID. function can be declared by name (text type) or OID. privilege is declared using a text string, which must be EXECUTE.

Return type: boolean

has_function_privilege(function, privilege)

Description: Queries whether the current user has permission for function.

Parameters: function can be declared by name (text type) or OID. privilege is declared using a text string, which must be EXECUTE.

Return type: boolean

Note: has_function_privilege checks whether a user can access a function in a particular way. Its argument possibilities are analogous to has_table_privilege. When a function is specified by a text string rather than by OID, the allowed input is the same as that for the regprocedure data type (see Object Identifier Types). The desired access permission type must evaluate to EXECUTE.

has_language_privilege(user, language, privilege)

Description: Queries whether a specified user has permission for language.

Parameters: user can be declared by name (text type) or OID. language can be declared by name (text type) or OID. privilege is declared using a text string, which must be USAGE.

Return type: boolean

has_language_privilege(language, privilege)

Description: Queries whether the current user has permission for language.

Parameters: language can be declared by name (text type) or OID. privilege is declared using a text string, which must be USAGE.

Return type: boolean

Note: has_language_privilege checks whether a user can access a procedural language in a particular way. Its argument possibilities are analogous to has_table_privilege. The desired access permission type must evaluate to USAGE.

has_schema_privilege(user, schema, privilege)

Description: Queries whether a specified user has permission for schema.

Parameters: user can be declared by name (text type) or OID. schema can be declared by name (text type) or OID. privilege is declared using a text string, which can be CREATE, USAGE, or multiple permission types separated by commas (,).

Return type: boolean

has_schema_privilege(schema, privilege)

Description: Queries whether the current user has permission for schema.

Parameters: schema can be declared by name (text type) or OID. privilege is declared using a text string, which can be CREATE, USAGE, or multiple permission types separated by commas (,).

Return type: boolean

Note: has_schema_privilege checks whether a user can access a schema in a particular way. Its argument possibilities are analogous to has_table_privilege. The desired access permission type must evaluate to some combination of CREATE or USAGE.

has_server_privilege(user, server, privilege)

Description: Queries whether a specified user has permission for foreign server.

Parameters: user can be declared by name (text type) or OID. server can be declared by name (text type) or OID. privilege is declared using a text string, which must be USAGE.

Return type: boolean

has_server_privilege(server, privilege)

Description: Queries whether the current user has permission for foreign server.

Parameters: server can be declared by name (text type) or OID. privilege is declared using a text string, which must be USAGE.

Return type: boolean

Note: has_server_privilege checks whether a user can access a foreign server in a particular way. Its argument possibilities are analogous to has_table_privilege. The desired access permission type must evaluate to USAGE.

has_table_privilege(user, table, privilege)

Description: Queries whether a specified user has permission for table.

Parameters: user can be declared by name (text type) or OID. table can be declared by name (text type) or OID. privilege is declared using a text string, which can be SELECT, INSERT, UPDATE, DELETE, TRUNCATE, REFERENCES, or TRIGGER, or multiple permission types separated by commas (,).

Return type: boolean

has_table_privilege(table, privilege)

Description: Queries whether the current user has permission for table.

Parameters: table can be declared by name (text type) or OID. privilege is declared using a text string, which can be SELECT, INSERT, UPDATE, DELETE, TRUNCATE, REFERENCES, or TRIGGER, or multiple permission types separated by commas (,).

Return type: boolean

has_table_privilege checks whether a user can access a table in a particular way. The user can be specified by name, by OID (pg_authid.oid), public to indicate the PUBLIC pseudo-role, or if the argument is omitted current_user is assumed. The table can be specified by name or by OID. When specifying by name, the name can be schema-qualified if necessary. If a text string is used to declare privilege, you can add WITH GRANT OPTION to the permission type to test whether the permission has the grant option. When there are multiple permission types, owning one of them will lead to a true result.

Example:

    
       SELECT has_table_privilege('tpcds.web_site', 'select');
 has_table_privilege  
--------------------- 
 t 
(1 row)

SELECT has_table_privilege('dbadmin', 'tpcds.web_site', 'select,INSERT WITH GRANT OPTION ');
 has_table_privilege  
--------------------- 
 t 
(1 row)

pg_has_role(user, role, privilege)

Description: Queries whether a specified user has permission for role.

Parameters: user can be declared by name (text type) or OID. role can be declared by name (text type) or OID. privilege is declared using a text string, which can be MEMBER, USAGE, or multiple permission types separated by commas (,).

Return type: boolean

pg_has_role(role, privilege)

Description: Specifies whether the current user has permission for role.

Parameters: role can be declared by name (text type) or OID. privilege is declared using a text string, which can be MEMBER, USAGE, or multiple permission types separated by commas (,).

Return type: boolean

Note: pg_has_role checks whether a user can access a role in a particular way. Its argument possibilities are analogous to has_table_privilege, except that public is not allowed as a user name. The desired access permission type must evaluate to some combination of MEMBER or USAGE. MEMBER denotes direct or indirect membership in the role (that is, the right to do SET ROLE), while USAGE denotes the permissions of the role are available without doing SET ROLE.