From 293913568e6a7a86fd1479e1cff8e2ecb58d6568 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 13 Apr 2024 15:44:03 +0200 Subject: Adding upstream version 16.2. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/infoschema-role-udt-grants.html | 53 +++++++++++++++++++++++ 1 file changed, 53 insertions(+) create mode 100644 doc/src/sgml/html/infoschema-role-udt-grants.html (limited to 'doc/src/sgml/html/infoschema-role-udt-grants.html') diff --git a/doc/src/sgml/html/infoschema-role-udt-grants.html b/doc/src/sgml/html/infoschema-role-udt-grants.html new file mode 100644 index 0000000..54d983c --- /dev/null +++ b/doc/src/sgml/html/infoschema-role-udt-grants.html @@ -0,0 +1,53 @@ + +37.38. role_udt_grants

37.38. role_udt_grants #

+ The view role_udt_grants is intended to identify + USAGE privileges granted on user-defined types + where the grantor or grantee is a currently enabled role. Further + information can be found under + udt_privileges. The only effective difference + between this view and udt_privileges is that + this view omits objects that have been made accessible to the + current user by way of a grant to PUBLIC. Since + data types do not have real privileges in PostgreSQL, but only an + implicit grant to PUBLIC, this view is empty. +

Table 37.36. role_udt_grants Columns

+ Column Type +

+

+ Description +

+ grantor sql_identifier +

+

+ The name of the role that granted the privilege +

+ grantee sql_identifier +

+

+ The name of the role that the privilege was granted to +

+ udt_catalog sql_identifier +

+

+ Name of the database containing the type (always the current database) +

+ udt_schema sql_identifier +

+

+ Name of the schema containing the type +

+ udt_name sql_identifier +

+

+ Name of the type +

+ privilege_type character_data +

+

+ Always TYPE USAGE +

+ is_grantable yes_or_no +

+

+ YES if the privilege is grantable, NO if not +


\ No newline at end of file -- cgit v1.2.3