Re: Better title output for psql \dt \di etc. commands

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Better title output for psql \dt \di etc. commands
Date: 2025-02-03 19:39:41
Message-ID: CAKAnmm+KtZ-Fh-fd87_99SVTPDLnwved+JrYFPW4YShJiJvOHg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 3, 2025 at 1:07 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> As presented, I think this fails the translatability guideline

Thanks, good point. Please find attached a slightly more verbose version
that should be better for translations.

For myself, if we were going to do something like this, I'd kind of like to
> cover more cases:
>
> greg=# \dti
> List of tables and indexes
>

I toyed with that for a bit, but as you say, without generating a ton of
combinations to translate, we'd have to fall back on run-time
constructions. Neither is ideal. I also realized that I almost never type
"\dti". Very common for me are \d and \dt and \dv etc. but combinations are
something I never bother with. At that point, I just do a \d. I think given
how rare (granted, anecdotally) those combinations are, it's okay if we
expose people to the "r" word.

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

Attachment Content-Type Size
0002-Show-more-intuitive-titles-for-psql-commands.patch application/octet-stream 3.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2025-02-03 19:51:15 Re: New GUC autovacuum_max_threshold ?
Previous Message Masahiko Sawada 2025-02-03 19:32:28 Re: pg_rewind with --write-recovery-conf option doesn't write dbname to primary_conninfo value.