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.98.2) (envelope-from ) id 1xBTJM-00000003DVR-3SWS for pgsql-docs@arkaria.postgresql.org; Tue, 29 Sep 2026 08:35:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xBTJL-0000000DpKH-3IiP for pgsql-docs@arkaria.postgresql.org; Tue, 29 Sep 2026 08:35:39 +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.98.2) (envelope-from ) id 1xBFWL-0000000Ao8j-2iWh for pgsql-docs@lists.postgresql.org; Mon, 28 Sep 2026 17:52:09 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xBFWI-00000001mN8-1pTG for pgsql-docs@lists.postgresql.org; Mon, 28 Sep 2026 17:52:09 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=lXye6uRjzugYewS1x+v6QS9N4NKhb5FqwYI1O4ipEDM=; b=Fe3q8PtdbQ9/b2Wldv7lkReZjZ LQA1OIDLusVjL10lG+WzTR4B3yXIjYzrEMvE36pRaZSqalsXFQc4i+X1MPqzHRj0c23sUA+Xp5+pS aqzq1DAyN6B5c5V4yl0we/aKCbMhBMEi0KukyChlpoQx5rUwlSgcEMOxfo+ZideIJ/3+Aw1fHAvfE CdOtrjN6kgx/ceAotLrvL6Q6j57gR2FqjO5cUdHg0gi0+Mb6OCf3xyAT1dpHNFbLdtIxCgSma+HkT 1cBdY8Ejr0KjL+ABNPgvuV0CRTTZjSTXQEeQ51PTmKVk0xI1PCMjBvoBjVeBFEMZtQdMLi5NEBTLl Bh03AxRA==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1xBFWG-0003UZ-2w for pgsql-docs@lists.postgresql.org; Mon, 28 Sep 2026 17:52:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xBFWF-0000000ErBE-2NYd for pgsql-docs@lists.postgresql.org; Mon, 28 Sep 2026 17:52:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: [Minor] Clarification on "2.7. Aggregate Functions" To: pgsql-docs@lists.postgresql.org From: PG Doc comments form Cc: matematica.a3k@gmail.com Reply-To: matematica.a3k@gmail.com, pgsql-docs@lists.postgresql.org Date: Mon, 28 Sep 2026 17:51:42 +0000 Message-ID: <179061790299.1026196.8971090344603809875@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/18/tutorial-agg.html Description: Where it says: "FILTER is much like WHERE, except that it removes rows only from the input of the particular aggregate function that it is attached to. Here, the count aggregate counts only rows with temp_lo below 45; but the max aggregate is still applied to all rows, so it still finds the reading of 46." Should say "FILTER is much like WHERE, except that it removes rows only from the input of the particular aggregate function that it is attached to. Here, the count aggregate counts only rows with temp_lo below 45; but the max aggregate is still applied to all rows being considered with the GROUP BY clause, so it still finds the reading of 46." Wording may vary, I think a clarification on this should be an improvement.