Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: Unclear documentation and requirement of clarification
To: pgsql-docs@lists.postgresql.org
From: PG Doc comments form <noreply@postgresql.org>
Cc: aravinat2001@gmail.com
Reply-To: aravinat2001@gmail.com, pgsql-docs@lists.postgresql.org
Date: Thu, 16 Apr 2026 13:32:48 +0000
Message-ID: <177634636825.403056.10912625029192163239@wrigleys.postgresql.org>
Auto-Submitted: auto-generated
Archived-At: 
 <https://www.postgresql.org/message-id/177634636825.403056.10912625029192163239%40wrigleys.postgresql.org>
Precedence: bulk

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/18/tutorial-agg.html
Description:

Notice this particular section in the documentation of 2.7 Aggregrate
Functions (https://www.postgresql.org/docs/current/tutorial-agg.html) :
"If we wanted to know what city (or cities) that reading occurred in, we
might try:

SELECT city FROM weather WHERE temp_lo =3D max(temp_lo);     -- WRONG
but this will not work since the aggregate max cannot be used in the WHERE
clause. (This restriction exists because the WHERE clause determines which
rows will be included in the aggregate calculation; so obviously it has to
be evaluated before aggregate functions are computed.) However, as is often
the case the query can be restated to accomplish the desired result, here by
using a subquery:

SELECT city FROM weather
    WHERE temp_lo =3D (SELECT max(temp_lo) FROM weather);"

This would be better off if it's mentioned that in this particular case, we
actually need the aggregate function to be computed before the WHERE clause
and that's why we are using a subquery.