Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lw4oc-00034G-Ic for pgsql-docs@arkaria.postgresql.org; Wed, 23 Jun 2021 15:29:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lw4oa-0004I7-Ks for pgsql-docs@arkaria.postgresql.org; Wed, 23 Jun 2021 15:29:20 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lw4oa-0004Hz-Es for pgsql-docs@lists.postgresql.org; Wed, 23 Jun 2021 15:29:20 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lw4oU-0000pu-2x for pgsql-docs@lists.postgresql.org; Wed, 23 Jun 2021 15:29:19 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 15NFTBIK2225087; Wed, 23 Jun 2021 11:29:11 -0400 From: Tom Lane To: "David G. Johnston" cc: aazamrafeeque0@gmail.com, Pg Docs Subject: Re: Incorrect Syntax in Function Syntax diagram In-reply-to: References: <162444349581.694.5818572718530259025@wrigleys.postgresql.org> Comments: In-reply-to "David G. Johnston" message dated "Wed, 23 Jun 2021 08:16:49 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2225084.1624462151.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 23 Jun 2021 11:29:11 -0400 Message-ID: <2225085.1624462151@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "David G. Johnston" writes: > On Wed, Jun 23, 2021 at 6:31 AM PG Doc comments form > wrote: > Please separate the [ NOT ] LEAKPROOF from the OR list > I would agree, and would add that I wonder whether the syntax for the th= ree > mutually exclusive options should be shown as such instead of having to > read that in the description notes. Does writing < | { IMMUTABLE | STAB= LE > | VOLATILE } > work? Yeah. The way it's written fails to show, except via formatting, that IMMUTABLE/STABLE/VOLATILE are mutually exclusive; and then somebody came along and destroyed the formatting. I agree both with adding braces and with putting LEAKPROOF on its own line. The latter is/should be only cosmetic; but the rest of the list has one line per independent option, and LEAKPROOF is surely independent of the volatility options. regards, tom lane