| PostgreSQL 9.2.4 Documentation | ||||
|---|---|---|---|---|
| Prev | Up | Chapter 34. The Information Schema | Next | |
The view table_privileges identifies all privileges granted on tables or views to a currently enabled role or by a currently enabled role. There is one row for each combination of table, grantor, and grantee.
Table 34-49. table_privileges 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 |
| table_catalog | sql_identifier | Name of the database that contains the table (always the current database) |
| table_schema | sql_identifier | Name of the schema that contains the table |
| table_name | sql_identifier | Name of the table |
| privilege_type | character_data | Type of the privilege: SELECT, INSERT, UPDATE, DELETE, TRUNCATE, REFERENCES, or TRIGGER |
| is_grantable | yes_or_no | YES if the privilege is grantable, NO if not |
| with_hierarchy | yes_or_no | In the SQL standard, WITH HIERARCHY OPTION is a separate (sub-)privilege allowing certain operations on table inheritance hierarchies. In PostgreSQL, this is included in the SELECT privilege, so this column shows YES if the privilege is SELECT, else NO. |
Please use this form to add your own comments regarding your experience with particular features of PostgreSQL, clarifications of the documentation, or hints for other users. Please note, this is not a support forum, and your IP address will be logged. If you have a question or need help, please see the faq, try a mailing list, or join us on IRC. Note that submissions containing URLs or other keywords commonly found in 'spam' comments may be silently discarded. Please contact the webmaster if you think this is happening to you in error.
Proceed to the comment form.