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 1vHDmG-000Hrl-Lr for pgsql-docs@arkaria.postgresql.org; Fri, 07 Nov 2025 04:08:45 +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 1vHDmF-00Bx8W-Cd for pgsql-docs@arkaria.postgresql.org; Fri, 07 Nov 2025 04:08:43 +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 1vHDmF-00Bx8O-5K for pgsql-docs@lists.postgresql.org; Fri, 07 Nov 2025 04:08:43 +0000 Received: from mout-u-204.mailbox.org ([80.241.59.204]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vHDmC-006QVU-38 for pgsql-docs@lists.postgresql.org; Fri, 07 Nov 2025 04:08:42 +0000 Received: from smtp202.mailbox.org (smtp202.mailbox.org [IPv6:2001:67c:2050:b231:465::202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-u-204.mailbox.org (Postfix) with ESMTPS id 4d2lsw2G96z9tPZ; Fri, 7 Nov 2025 05:08:36 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ewie.name; s=MBO0001; t=1762488516; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=yQ5KdS2FkT9Xn40HgY/ThIlV28eJg5aaQ2clL4KP220=; b=YdLlhHSgbzwiZOBPri6iaivj0JXtA3EeEYrZfz7HB7Qyrpdqkk4yZb0q49JoLZpw7zDddb YVM0X0ah7enmmWRJGw0ckV5rLSjGtjN5lzzel0iu3J3P70z5o2EF14jAw6NAzossbbWHXy 0uB56zhgdS9gwqHc/LPKlagT31SetfIvMezetJtiRZP3J/gQsL8235JRFcRRpdcN7kbi2u l1y2PUz1I9Lbr+ytEotwka0cNTQpMYFaUjyZ/g2NDRM/uqqoXNZvY+ff31F9DFjNM+cbqZ vZMZqy3zYN4CmqUq1zJpNK592p9GFgk4dXZ5qzPQVZEdA7ZQ+cTS/6NUP182Fg== Authentication-Results: outgoing_mbo_mout; dkim=none; spf=pass (outgoing_mbo_mout: domain of ewie@ewie.name designates 2001:67c:2050:b231:465::202 as permitted sender) smtp.mailfrom=ewie@ewie.name Date: Fri, 7 Nov 2025 05:08:27 +0100 From: Erik Wienhold To: Daisuke Higuchi Cc: pgsql-docs@lists.postgresql.org Subject: Re: doc: Fix missing or duplicate closing parentheses in some documents Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4d2lsw2G96z9tPZ List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2025-11-07 02:40 +0100, Daisuke Higuchi wrote: > I found that the parentheses seemed not to be handled correctly in > following 3 documents, so I attach the patch for this. > > - closing parentheses is missing > - doc/src/sgml/client-auth.sgml > > - closing parentheses is duplicate > - doc/src/sgml/ltree.sgml > - doc/src/sgml/trigger.sgml All three changes make sense. Although I would rephrase the part in client-auth.sgml from this: "a regular expression (when starting with a slash (/))" to this: "a regular expression starting with a slash (/)" The latter reads nicer IMO and avoids the double closing parenthesis which I find a bit awkward. -- Erik Wienhold