Re: psql: Option to use expanded mode for various meta-commands

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
To: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: psql: Option to use expanded mode for various meta-commands
Date: 2025-01-08 13:43:57
Message-ID: CAEZATCUyLVQ-Ara0=944ubJY3t0qCiGz7e1o0tgftue3g-jLew@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 30 Dec 2024 at 15:48, Greg Sabino Mullane <htamfids(at)gmail(dot)com> wrote:
>
> I like this, very useful. It's a shame about the conflict with \dx (lesson for the future: think extra carefully about option namings!). I am impressed that \dx \d \d+ \d+x and even \dxx all work as one might intuit with this patch.
>

Thanks for looking.

Attached is a more complete patch, now with
- trivial bug-fix for previous \d code, per cfbot
- expanded mode support for \l and \z
- updated psql help
- a few representative regression test cases

The majority of the patch is doc updates, which are somewhat tedious.
Initially, I resisted documenting the 'x' option in the description of
every command affected, but given the length of the list of commands
in the HTML page, it's a long way from any given command to the top or
bottom where 'x' is described in more detail. So in the end, I decided
to just add a sentence to each command's description, keeping it as
short as possible.

Regards,
Dean

Attachment Content-Type Size
psql-meta-cmds-expanded-mode-v2.patch text/x-patch 63.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Frédéric Yhuel 2025-01-08 13:48:10 Re: New GUC autovacuum_max_threshold ?
Previous Message Peter Eisentraut 2025-01-08 13:41:50 Re: Virtual generated columns