Re: Unclear documentation and requirement of clarification

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: "aravinat2001(at)gmail(dot)com" <aravinat2001(at)gmail(dot)com>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org>
Subject: Re: Unclear documentation and requirement of clarification
Date: 2026-04-18 06:29:20
Message-ID: CAKFQuwa=LNL8Ub-8ShCvpg4N2u_+MeVRSYRNC8Qj=0Zajp01+g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Thursday, April 16, 2026, PG Doc comments form <noreply(at)postgresql(dot)org>
wrote:

> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/18/tutorial-agg.html
> Description:
>
> (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.)
>
> 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.
>
>
That is what the parenthetical says, though without introducing the term
subquery.

Without a question or a concrete proposed alternative leaving this as-is
seems reasonable. I have no qualms with it at least.

David J.

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message David G. Johnston 2026-04-18 07:01:45 Re: Temporary tables and Write-Ahead Log
Previous Message Víctor Herraiz Posada 2026-04-18 00:27:25 Temporary tables and Write-Ahead Log