From: | Srinath Reddy <srinath2133(at)gmail(dot)com> |
---|---|
To: | Mahendra Singh Thalor <mahi6run(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [Proposal] Add \dAt [AMPTRN [TBLPTRN]] to list tables by Table Access Method in psql |
Date: | 2025-04-15 11:56:27 |
Message-ID: | CAFC+b6pk-HoRkPbCUy6OTenJ1wV0aMqayXMhp7woLc7-s_fpgg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On Tue, Apr 15, 2025 at 3:22 PM Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>
wrote:
>
> I think we can get both the details by SELECT command.
Thanks for the input!
While it's true that we can use catalog queries to get this info, the main
goal of adding a \dAt command or "\"[Informational] commands is to
improve *user
experience and discoverability*. Not everyone wants to write or remember
complex queries — having a direct command helps users quickly inspect TAM
usage, especially when working with multiple forks or extensions.
Additionally,
> this info should be visible by the admin only because there is no use
> case for the user to know all the tables from one TAM.
>
I don’t think this information should be restricted to admins. When
specialized TAMs are in use, it’s actually valuable for users to know which
TAM a table is using. This helps them understand how best to interact with
the table and structure their workloads to align with the TAM's intended
access patterns.
Thanks,
Srinath Reddy Sadipiralla
EDB: https://www.enterprisedb.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2025-04-15 12:31:50 | Re: [PoC] Federated Authn/z with OAUTHBEARER |
Previous Message | Ranier Vilela | 2025-04-15 11:53:43 | Silence using uninitialized value |