Re: alphabetize long options in pg_dump[all] docs

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql(at)j-davis(dot)com
Subject: Re: alphabetize long options in pg_dump[all] docs
Date: 2025-04-29 21:54:38
Message-ID: aBFKnj-RVxNsf_qo@nathan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Apr 29, 2025 at 11:45:11PM +0200, Álvaro Herrera wrote:
> I think the concept here is that all short options go first in
> alphabetical order, then the long options in their own alphabetical
> order, and if one option has both, then the short option takes
> precedence.

That's what it looks like to me, too.

> If that's the idea, then --filter in pg_dumpall is in the
> wrong place, and other than that it looks good.

I missed that one, thanks.

> I think that's what gives the shorter patch. But where would you look
> for, say, --large-objects? I mean, how do you know that its short
> version is -b? Maybe it would make more sense to sort on long options
> first and put short options as the second-priority item for each option.

Fair point. We seem to be pivoting towards long options, anyway. If
there's support for this, I could go through all the client and server
application docs to ensure they match this style.

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2025-04-29 22:51:38 Re: Adding skip scan (including MDAM style range skip scan) to nbtree
Previous Message Salvatore Dipietro 2025-04-29 21:49:14 Remove Instruction Synchronization Barrier in spin_delay() for ARM64 architecture