(I sort of agree with the parent, in that, if you need this in a raw SQL interface, it's a pain. But it shouldn't be a common pain point?)
In pgAdmin I would have to expand every schema to see every table.
Was a bit tired when writing that comment.
(I'm a CLI user, so it's a \dt away. But I Googled screenshots of pgAdmin prior to commenting to see if it was in the UI, and it/was.)
It also reminds me how many DBMSs did not support the LIMIT clause because it is non-standard. But it is good from a usability perspective.
https://stackoverflow.com/questions/1528604/how-universal-is...
That's why ClickHouse has support for most of the extensions from the MySQL dialect.
Admittedly the internal tables and views have a bit of a learning curve and are a little bit obscure (and inconsistent) at times, but it's much nicer and much more flexible.
The CLI stuff like \d are just "aliases" for queries; \set echo_hidden shows them.
From the CLI \d etc. seems just as easy (easier actually), and you can add your own shortcuts if you want.
From outside the CLI, this sort of introspection is rare enough I don't really see the point in making special shortcuts for it.