| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: --sync-method isn't documented to take an argument |
| Date: | 2023-10-04 14:56:35 |
| Message-ID: | 20231004145635.GB3178@nathanxps13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 04, 2023 at 09:08:57AM -0400, Robert Haas wrote:
> The various command-line utilities that have recently acquired a
> --sync-method option document it like this:
>
> <term><option>--sync-method</option></term>
>
> But that is not how we document options which take an argument. We do
> it like this:
>
> <term><option>--pgdata=<replaceable>directory</replaceable></option></term>
> <term><option>--filenode=<replaceable>filenode</replaceable></option></term>
>
> etc.
>
> This one should be something like this:
>
> <term><option>--sync-method=<replaceable>method</replaceable></option></term>
Whoops. Thanks for pointing this out. I'll get this fixed.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2023-10-04 14:56:54 | Re: --sync-method isn't documented to take an argument |
| Previous Message | Nathan Bossart | 2023-10-04 14:52:11 | Re: stopgap fix for signal handling during restore_command |