| schema | name | column | data type |
|---|---|---|---|
| pg_catalog | sys_mv_state | base_table_database_name | char(128) |
| pg_catalog | sys_mv_state | base_table_name | char(128) |
| pg_catalog | sys_mv_state | base_table_schema | char(128) |
| pg_catalog | sys_mv_state | database_name | char(128) |
| pg_catalog | sys_mv_state | event_desc | char(500) |
| pg_catalog | sys_mv_state | mv_name | char(128) |
| pg_catalog | sys_mv_state | mv_schema | char(128) |
| pg_catalog | sys_mv_state | start_time | timestamp |
| pg_catalog | sys_mv_state | state | char(32) |
| pg_catalog | sys_mv_state | transaction_id | int8 |
| pg_catalog | sys_mv_state | user_id | int8 |
Error: describing system view <sys_mv_state> is disabled.
Note the AWS are as you see here censoring the SQL of more recent system tables views. This is problematic, as the docs are no good, and so it's not uncommon to need to view the text to make sense of the output. I am of the view AWS, at least as far as Redshift are concerned, has a culture of secrecy and I see this as more of the same. I can see absolutely no reason or benefit, for users, for censoring the view text.
Home 3D Друк Blog Bring-Up Times Consultancy Cross-Region Benchmarks Email Forums IRC Mailing Lists Reddit Redshift Price Tracker Redshift Version Tracker Redshift Workbench System Table Tracker The Known Universe Twitter White Papers