| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, 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-30 14:46:37 |
| Message-ID: | 202504301446.a5ytr5imh5el@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2025-Apr-30, Peter Eisentraut wrote:
> On 29.04.25 23:54, Nathan Bossart wrote:
> > 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.
>
> However, I think this would require coordination across all --help output
> and man pages (76 objects), so for the short term, let's just move recently
> added options to the right place under the current theory/theories, and
> leave a larger reshuffling for later.
+1 WFM
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Pero la cosa no es muy grave ..." (le petit Nicolas -- René Goscinny)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yura Sokolov | 2025-04-30 14:55:43 | Re: [RFC] Lock-free XLog Reservation from WAL |
| Previous Message | Junwang Zhao | 2025-04-30 14:07:36 | Re: Introduce some randomness to autovacuum |