Describe the bug
The tree view is really nice to understand the scans, joins, and rows, but without the name of the tables / indexes I can't use it without constantly switching to other views:
In this example, one SeqScan is flagged as critical, but we don't know which table is scanned.
Expected behavior
I think we need at least the table or index name for the scan nodes (with the alias). It can be large and make the node less readable, but for the scans, which are always leaves in the tree, it could be displayed below the node.
Describe the bug
The tree view is really nice to understand the scans, joins, and rows, but without the name of the tables / indexes I can't use it without constantly switching to other views:
In this example, one SeqScan is flagged as critical, but we don't know which table is scanned.
Expected behavior
I think we need at least the table or index name for the scan nodes (with the alias). It can be large and make the node less readable, but for the scans, which are always leaves in the tree, it could be displayed below the node.