Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qo3cN-0000b8-Gk for pgsql-hackers@arkaria.postgresql.org; Wed, 04 Oct 2023 15:16:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qo3cM-00H2fn-0E for pgsql-hackers@arkaria.postgresql.org; Wed, 04 Oct 2023 15:16:54 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qo3cL-00H2fO-Ls for pgsql-hackers@lists.postgresql.org; Wed, 04 Oct 2023 15:16:53 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qo3cJ-00012y-Rw for pgsql-hackers@postgresql.org; Wed, 04 Oct 2023 15:16:53 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id F3C0C2FB197A for ; Wed, 4 Oct 2023 17:16:50 +0200 (CEST) Received: from s979.loopia.se (unknown [172.22.191.5]) by s807.loopia.se (Postfix) with ESMTP id E40092E298ED; Wed, 4 Oct 2023 17:16:50 +0200 (CEST) Received: from s471.loopia.se (unknown [172.22.191.6]) by s979.loopia.se (Postfix) with ESMTP id E18E410BC38C; Wed, 4 Oct 2023 17:16:50 +0200 (CEST) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1 X-Spam-Level: X-Spam-Status: No, score=-1 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1] autolearn=disabled Received: from s980.loopia.se ([172.22.191.5]) by s471.loopia.se (s471.loopia.se [172.22.190.35]) (amavisd-new, port 10024) with LMTP id ZiRYe9Sd1yig; Wed, 4 Oct 2023 17:16:50 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 38.140.183.210 Received: from smtpclient.apple (unknown [38.140.183.210]) (Authenticated sender: daniel@yesql.se) by s980.loopia.se (Postfix) with ESMTPSA id 01A4D2201524; Wed, 4 Oct 2023 17:16:49 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.3\)) Subject: Re: --sync-method isn't documented to take an argument From: Daniel Gustafsson In-Reply-To: <2589228.1696432027@sss.pgh.pa.us> Date: Wed, 4 Oct 2023 17:16:48 +0200 Cc: Alvaro Herrera , Robert Haas , PostgreSQL Hackers , Nathan Bossart Content-Transfer-Encoding: quoted-printable Message-Id: References: <202310041435.5ss4bpih2lal@alvherre.pgsql> <2585706.1696430390@sss.pgh.pa.us> <5FA50A84-6ECC-4280-AC2E-23F88C252713@yesql.se> <2586962.1696431119@sss.pgh.pa.us> <8CF2C172-4500-4A77-95DF-900F363D7196@yesql.se> <2589228.1696432027@sss.pgh.pa.us> To: Tom Lane X-Mailer: Apple Mail (2.3696.120.41.1.3) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 4 Oct 2023, at 17:07, Tom Lane wrote: > OK, so now I know what the possible values of "class" are, but > I'm still not seeing a reason why we shouldn't just assume that > "parameter" is the only one of interest. I think "parameter" is the only one of interest for this usecase (params = to application options), but it might not necessarily be applicable to = other uses of we have in the tree, like for example in bki.sgml: oprname(lefttype,righttype) But since we don't know if anyone is rendering our docs with a custom = style, or ever will, this is all very theoretical. Maybe skipping the class = attribute is the right choice for consistency? -- Daniel Gustafsson