Re: [PATCH] psql: add size-based sorting options (O/o) for tables and indexes

From: "Euler Taveira" <euler(at)eulerto(dot)com>
To: M(dot)Atıf Ceylan <mehmet(at)atifceylan(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] psql: add size-based sorting options (O/o) for tables and indexes
Date: 2025-11-26 12:43:38
Message-ID: 84647ed5-9302-4c1e-8364-6c575cee20b0@app.fastmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 26, 2025, at 4:48 AM, M.Atıf Ceylan wrote:
> Hello,
> This patch adds two new meta-command modifiers for \dt(+) and \di(+):
>
> - O : sort by total relation size descending
> - o : sort by total relation size ascending
>

Thanks for your contribution. Register your patch in the next commitfest [1] so
we don't loose track of it.

I didn't look at your patch but I was wondering if a general solution isn't a
better way to add this feature. I wouldn't modify these specific psql
meta-commands, instead, I would add a new psql meta-command that defines this
property for all objects if applicable.

\sort [ name | size [ asc | desc ] ]

I thought about a list to be cover other sort cases too but if things starting
to be complex, it is time to write your own query.

With a parameter, it appends the ORDER BY clause in the SQL commands executed by
psql if applicable. Without a parameter, it uses the current behavior.

[1] https://commitfest.postgresql.org/57/

--
Euler Taveira
EDB https://www.enterprisedb.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kirill Reshke 2025-11-26 12:50:01 Re: [PATCH] Add native PIVOT syntax for SQL Server/Oracle compatibility
Previous Message Matthias van de Meent 2025-11-26 12:18:39 Re: Patch: VACUUM should ignore (CREATE |RE)INDEX CONCURRENTLY for xmin horizon calculations