Re: psql \dh: List High-Level (Root) Tables and Indexes - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: psql \dh: List High-Level (Root) Tables and Indexes
Date
Msg-id CAKAnmmJToEu6MYeddUhmT4-6yJ0xKM_YhKMqjD=WmK+hHi-6Tw@mail.gmail.com
Whole thread Raw
In response to Re: psql \dh: List High-Level (Root) Tables and Indexes  (Sadeq Dousti <msdousti@gmail.com>)
Responses Re: psql \dh: List High-Level (Root) Tables and Indexes
List pgsql-hackers
On Sun, Feb 23, 2025 at 4:34 PM Sadeq Dousti <msdousti@gmail.com> wrote:
Totally agree about the naming. There's no other terminology known to me, but I'll definitely think about it. Of course, I'm very open to
suggestions from you or anyone else in the community.

The problem is that we are really tight on available letters for a bare \d. I immediately thought of "adult" tables (those that are not children). But both \da and \dA are used! The only other mnemonic option is "\de" where e stands for elder tables (get it? elder because they are not children).

Would it be useful to you to have them as separate items? In other words, not indexes and tables together, but some flag on both \dt and \di to limit to non-child relations. I think as far as "core structure" the list of tables is far more important than what indexes happen to be on them. Plus, \d also shows sequences, which is even less useful information than indexes, IMHO.

So maybe \dta and \dia? (adults only)

Cheers,
Greg

--
Enterprise Postgres Software Products & Tech Support

pgsql-hackers by date:

Previous
From: Andrei Lepikhov
Date:
Subject: Re: Removing unneeded self joins
Next
From: Daniel Gustafsson
Date:
Subject: Re: [PoC] Federated Authn/z with OAUTHBEARER