The rows returned are limited to the routines the user is privileged to interact with.
Note
Currently, users with the MANAGE privilege on an object cannot view all grants for that object in the INFORMATION_SCHEMA. Instead, the INFORMATION_SCHEMA only shows grants their own grants on the object. This behavior will be corrected in the future.
Users with MANAGE privilege can view all grants on an object using SQL commands or Catalog Explorer. See Manage privileges in Unity Catalog.
Definition
The ROUTINE_PRIVILEGES relation contains the following columns:
Name
Data type
Nullable
Standard
Description
GRANTOR
STRING
No
Yes
Principal who granted the privilege.
GRANTEE
STRING
No
Yes
Principal to which the privilege is granted.
SPECIFIC_CATALOG
STRING
No
Yes
Catalog of routine on which the privilege is granted.
SPECIFIC_SCHEMA
STRING
No
Yes
Database of routine on which the privilege is granted.
SPECIFIC_NAME
STRING
No
Yes
Schema unique (specific) name of routine on which the privilege is granted.
ROUTINE_CATALOG
STRING
No
Yes
Matches SPECIFIC_CATALOG.
ROUTNE_SCHEMA
STRING
No
Yes
Matches SPECIFIC_SCHEMA.
ROUTINE_NAME
STRING
No
Yes
Name of routine on which the privilege is granted.
PRIVILEGE_TYPE
STRING
No
Yes
Privilege being granted.
IS_GRANTABLE
STRING
No
Yes
Always NO. Reserved for future use.
INHERITED_FROM
STRING
Yes
No
The ancestor relation that the privilege is inherited from.
Constraints
The following constraints apply to the ROUTINE_PRIVILEGES relation:
Relational databases can store vast quantities of data, but they also need to hold information about the structure of that data. For an operational database management system (DBMS) information about the structure of tables, and all other objects, security, and concurrency, amongst many other settings and metrics, is required. This information is know as metadata and is stored in system catalogs in Azure Database for PostgreSQL. In addition to directly accessing system catalogs, you can access system views