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

From David G. Johnston
Subject Re: psql \dh: List High-Level (Root) Tables and Indexes
Date
Msg-id CAKFQuwZetSzsEQgFLrCcgtJW-T6OZjyUOTs2s8vNWgDsm=N5zQ@mail.gmail.com
Whole thread Raw
In response to Re: psql \dh: List High-Level (Root) Tables and Indexes  (Greg Sabino Mullane <htamfids@gmail.com>)
Responses Re: psql \dh: List High-Level (Root) Tables and Indexes
List pgsql-hackers
On Sun, Feb 23, 2025 at 4:31 PM Greg Sabino Mullane <htamfids@gmail.com> wrote:
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).


How about:
\pset partition_roots_only 'true'

Then update all relevant queries to respect it.

That way no learning new ways to get the information you want but instead can set a global filter to suppress those child nodes that really don't need to be seen normally.

It would be nice if "N partition children suppressed due to partition_roots_only" would appear in the output somewhere if going this direction.

David J.

pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Statistics Import and Export
Next
From: Michael Paquier
Date:
Subject: Re: Remove wal_[sync|write][_time] from pg_stat_wal and track_wal_io_timing