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 1vBTnj-00H8BN-M6 for pgsql-docs@arkaria.postgresql.org; Wed, 22 Oct 2025 08:02:30 +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 1vBTnh-00EEFV-G1 for pgsql-docs@arkaria.postgresql.org; Wed, 22 Oct 2025 08:02:28 +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 1vBTnh-00EEFN-4z for pgsql-docs@lists.postgresql.org; Wed, 22 Oct 2025 08:02:28 +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.96) (envelope-from ) id 1vBTne-003Zxz-0L for pgsql-docs@lists.postgresql.org; Wed, 22 Oct 2025 08:02:27 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 5344B42309E for ; Wed, 22 Oct 2025 10:02:25 +0200 (CEST) Received: from s979.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id 448774225E9; Wed, 22 Oct 2025 10:02:25 +0200 (CEST) Received: from localhost (unknown [172.22.191.5]) by s979.loopia.se (Postfix) with ESMTP id 3D2E110BC4CF; Wed, 22 Oct 2025 10:02:25 +0200 (CEST) X-Virus-Scanned: amavis at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.2 X-Spam-Level: X-Spam-Status: No, score=-1.2 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1] autolearn=disabled Authentication-Results: s470.loopia.se (amavis); dkim=pass (2048-bit key) header.d=yesql.se Received: from s899.loopia.se ([172.22.191.6]) by localhost (s470.loopia.se [172.22.190.34]) (amavis, port 10024) with UTF8LMTP id AO_EhDeA1nqm; Wed, 22 Oct 2025 10:02:24 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.236 Received: from smtpclient.apple (customer-89-255-232-236.stosn.net [89.255.232.236]) (Authenticated sender: daniel@yesql.se) by s899.loopia.se (Postfix) with ESMTPSA id 909882C8BAEA; Wed, 22 Oct 2025 10:02:24 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yesql.se; s=loopiadkim1707475645; t=1761120144; bh=Y0ycEsKGvQNO99aK8AxNKfVZcsy7cHvb4E3j9urVgFE=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=IBDw3tqqJkD4Mj58TO+fBIaCUxk+i8Xk2BJ/M5SvZXJjD3emeKBH4YqMYMCLUFvPv IHGDFb0e3XSj/192N5MEDv3yIfge2FqPeJ3ePxbucuiV/FVrN/Iyaeu62SWgiWuAPK GgPJjwdxn2dOMAKNdWz3Zh4SwioxGq9jm91rw46XQD7+6HUHs5/mfpi4M+qU4MNcu+ xeEUPJo5MFnbw1aek4/HO4ZTKEWVH5VsmZ6h+VkfA7b3RDq5zNNDScPo7623qvekXQ AyMU5f1sqPPyCj8b6lQY2o6eMJnIkOksBIDEywt/03GMcVYSWWX68HBMXcQGLbmO5s o2dqk+gSNeOLA== Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.2\)) Subject: Re: Documentation improvement patch From: Daniel Gustafsson In-Reply-To: Date: Wed, 22 Oct 2025 10:02:14 +0200 Cc: pgsql-docs@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <84E4E3E6-D702-4604-AE0B-AF92B80B3833@yesql.se> References: <3881A97B-0146-4389-9C39-3C596536750B@yesql.se> To: Oleg X-Mailer: Apple Mail (2.3776.700.51.11.2) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 13 Oct 2025, at 12:51, Oleg wrote: > - COPY and other functions which allow executing a > + the COPY command and functions, which allow = executing a > I'm not sure about these, I think we use COPY without the the "the = COPY > command" decoration in many places so I think it's more consistent = like this. >=20 > I actually think we should add the decoration here because = "COPY and other file-access functions" > sounds a bit confusing since COPY is not a file-access function and we = seem to put it in the list. Even though I=20 > agree that everybody knows COPY is a command, not a function. We refer to SQL commands by just their names all over the documentation = without saying "an EXPLAIN command" etc, and I think this falls in that same = category. > - to call functions defined in the standard internal library, by using = an > + to call functions defined in the standard internal function library = by using an > interface similar to their SQL signature. > Isn't it a bit redundant to say "internal function library" when we = are already > talking about function definitions? >=20 > I agree that it may seem redundant, I added "function" here for the = sake of consistency with lines 1829/1830 (if applied to the master = branch) > where the documentation mentions "standard internal function library". I hadn't seen that, but with that in mind I agree that being consistent = is good so I'll withdraw that comment. -- Daniel Gustafsson