From d34e142c511c779a294ce96eee0e9ab535b24de3 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Thu, 23 Jun 2011 22:12:46 +0300 Subject: Add information schema views role_udt_grants, udt_privileges, user_defined_types --- doc/src/sgml/information_schema.sgml | 367 +++++++++++++++++++++++++++++++++++ 1 file changed, 367 insertions(+) (limited to 'doc/src') diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml index 40c0066d8ed..ab9ce2aa4a8 100644 --- a/doc/src/sgml/information_schema.sgml +++ b/doc/src/sgml/information_schema.sgml @@ -3509,6 +3509,81 @@ ORDER BY c.ordinal_position; + + <literal>role_udt_grants</literal> + + + 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. + + + + <literal>role_udt_grants</literal> Columns + + + + + Name + Data 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 + + + +
+ + <literal>role_usage_grants</literal> @@ -5499,6 +5574,80 @@ ORDER BY c.ordinal_position; + + <literal>udt_privileges</literal> + + + The view udt_privileges is intended to identify + USAGE privileges granted on user-defined types + to a currently enabled role or by a currently enabled role. Since + data types do not have real privileges + in PostgreSQL, this view shows implicit + non-grantable USAGE privileges granted by the + owner to PUBLIC for all types, including + built-in ones (except domains, + see for that). + + + + <literal>udt_privileges</literal> Columns + + + + + Name + Data Type + Description + + + + + + grantor + sql_identifier + Name of the role that granted the privilege + + + + grantee + sql_identifier + 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 + + + +
+ + <literal>usage_privileges</literal> @@ -5585,6 +5734,224 @@ ORDER BY c.ordinal_position; + + <literal>user_defined_types</literal> + + + The view user_defined_types currently contains + all composite types defined in the current database. + + + + SQL knows about two kinds of user-defined types: structured types + (also known as composite types + in PostgreSQL) and distinct types (not + implemented in PostgreSQL). To be + future-proof, use the + column user_defined_type_category to + differentiate between these. Other user-defined types such as base + types and enums, which are PostgreSQL + extensions, are not shown here. For domains, + see instead. + + + + <literal>user_defined_types</literal> Columns + + + + + Name + Data Type + Description + + + + + + user_defined_type_catalog + sql_identifier + Name of the database that contains the type (always the current database) + + + + user_defined_type_schema + sql_identifier + Name of the schema that contains the type + + + + user_defined_type_name + sql_identifier + Name of the type + + + + user_defined_type_category + character_data + + Currently always STRUCTURED + + + + + is_instantiable + yes_or_no + Applies to a feature not available in PostgreSQL + + + + is_final + yes_or_no + Applies to a feature not available in PostgreSQL + + + + ordering_form + character_data + Applies to a feature not available in PostgreSQL + + + + ordering_category + character_data + Applies to a feature not available in PostgreSQL + + + + ordering_routine_catalog + sql_identifier + Applies to a feature not available in PostgreSQL + + + + ordering_routine_schema + sql_identifier + Applies to a feature not available in PostgreSQL + + + + ordering_routine_name + sql_identifier + Applies to a feature not available in PostgreSQL + + + + reference_type + character_data + Applies to a feature not available in PostgreSQL + + + + data_type + character_data + + Always USER-DEFINED TYPE (for joining + against object_type columns in other + views) + + + + + character_maximum_length + cardinal_number + Applies to a feature not available in PostgreSQL + + + + character_octet_length + cardinal_number + Applies to a feature not available in PostgreSQL + + + + character_set_catalog + sql_identifier + Applies to a feature not available in PostgreSQL + + + + character_set_schema + sql_identifier + Applies to a feature not available in PostgreSQL + + + + character_set_name + sql_identifier + Applies to a feature not available in PostgreSQL + + + + collation_catalog + sql_identifier + Applies to a feature not available in PostgreSQL + + + + collation_schema + sql_identifier + Applies to a feature not available in PostgreSQL + + + + collation_name + sql_identifier + Applies to a feature not available in PostgreSQL + + + + numeric_precision + cardinal_number + Applies to a feature not available in PostgreSQL + + + + numeric_precision_radix + cardinal_number + Applies to a feature not available in PostgreSQL + + + + numeric_scale + cardinal_number + Applies to a feature not available in PostgreSQL + + + + datetime_precision + cardinal_number + Applies to a feature not available in PostgreSQL + + + + interval_type + character_data + Applies to a feature not available in PostgreSQL + + + + interval_precision + character_data + Applies to a feature not available in PostgreSQL + + + + source_dtd_identifier + sql_identifier + Applies to a feature not available in PostgreSQL + + + + ref_dtd_identifier + sql_identifier + Applies to a feature not available in PostgreSQL + + + +
+ + <literal>user_mapping_options</literal> -- cgit v1.2.3