Wholeheartedly agree about the need for better and bidirectional tools. That said, while I appreciate MySQLWorkbench and its ERD generation skills, I have never

Wholeheartedly agree about the need for better and bidirectional tools. That said, while I appreciate MySQLWorkbench and its ERD generation skills, I have never seen anything sufficiently powerful to document the features in a more feature-rich database like Postgres. For example: • knowing where the partial indexes are and what their defined subset is • domain types, their base type, and their defined subset • row-level access policies • trigger order, dependencies, and dependents (I think auto-generated sequence diagrams would do wonders here) • table partitioning hierarchy • constraint info or at least an identifiable visible marker for CHECK and EXCLUSION constraints • marking computed columns and materialized views • association between functions/procedures and the relations they read/write from in addition to cataloging pure functions • notation when a view is updatable • users/groups/roles and a view into the resources each have access to the system That's off the top of my head. I'm sure others can think of more. I realize these aren't trivial asks, but great tools rarely are. The existing ERD generators I've seen like MySQLWorkbench are good for basic bootstrapping or strictly the database users. I want to see more for the DB admin/developer cohort. I want a Javadoc+PlantUML for databases.