From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
---|---|
To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
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:45:11 |
Message-ID: | 202504292145.xubywjefezht@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2025-Apr-29, Nathan Bossart wrote:
> I noticed some of the new pg_dump[all] long options (e.g., --with-data,
> --statistics-only) are not listed in alphabetical order in the docs.
> Attached is a patch to fix that.
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. If that's the idea, then --filter in pg_dumpall is in the
wrong place, and other than that it looks good.
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.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"¿Qué importan los años? Lo que realmente importa es comprobar que
a fin de cuentas la mejor edad de la vida es estar vivo" (Mafalda)
From | Date | Subject | |
---|---|---|---|
Next Message | Salvatore Dipietro | 2025-04-29 21:49:14 | Remove Instruction Synchronization Barrier in spin_delay() for ARM64 architecture |
Previous Message | Nathan Bossart | 2025-04-29 21:36:20 | Re: allow changing autovacuum_max_workers without restarting |