Re: --sync-method isn't documented to take an argument

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: --sync-method isn't documented to take an argument
Date: 2023-10-04 19:50:59
Message-ID: 20231004195059.GA102574@nathanxps13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 04, 2023 at 12:24:36PM -0400, Tom Lane wrote:
> In any case, trying to standardize this looks like it would be a
> huge amount of churn for very little gain. I'd recommend making
> your markup look similar to what's immediately adjacent, if possible,
> and not sweating too much otherwise.

I matched the adjacent options as you suggested. Perhaps unsurprisingly,
the inclusion of class="parameter" is not the only inconsistency. I also
found that pg_upgrade adds the </option> before the argument name!

--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Jones 2023-10-04 20:03:38 Add annotation syntax to pg_hba.conf entries
Previous Message Robert Haas 2023-10-04 19:33:27 Re: trying again to get incremental backup