database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-12-19 17:02:53 +03:00
Code Activity

Document evaluation-order considerations for aggregate functions.

Browse Source 
The SELECT reference page didn't really address the question of when
aggregate function evaluation occurs, nor did the "expression evaluation
rules" documentation mention that CASE can't be used to control whether
an aggregate gets evaluated or not.  Improve that.

Per discussion of bug #11661.  Original text by Marti Raudsepp and Michael
Paquier, rewritten significantly by me.
This commit is contained in:
Tom Lane
2014-11-14 17:19:29 -05:00
parent 80eacaa3cd
commit 0ce627d465
2 changed files with 48 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
doc/src/sgml/ref/select.sgml
View File

@@ -109,9 +109,11 @@ TABLE [ ONLY ] <replaceable class="parameter">table_name</replaceable> [ * ]
<listitem>
<para>
If the <literal>GROUP BY</literal> clause is specified, the
If the <literal>GROUP BY</literal> clause is specified,
or if there are aggregate function calls, the
output is combined into groups of rows that match on one or more
values. If the <literal>HAVING</literal> clause is present, it
values, and the results of aggregate functions are computed.
If the <literal>HAVING</literal> clause is present, it
eliminates groups that do not satisfy the given condition. (See
<xref linkend="sql-groupby" endterm="sql-groupby-title"> and
<xref linkend="sql-having" endterm="sql-having-title"> below.)
@@ -637,17 +639,22 @@ GROUP BY <replaceable class="parameter">expression</replaceable> [, ...]
<para>
Aggregate functions, if any are used, are computed across all rows
making up each group, producing a separate value for each group
(whereas without <literal>GROUP BY</literal>, an aggregate
produces a single value computed across all the selected rows).
The set of rows fed to the aggregate function can be further filtered by
making up each group, producing a separate value for each group.
(If there are aggregate functions but no <literal>GROUP BY</literal>
clause, the query is treated as having a single group comprising all
the selected rows.)
The set of rows fed to each aggregate function can be further filtered by
attaching a <literal>FILTER</literal> clause to the aggregate function
call; see <xref linkend="syntax-aggregates"> for more information. When
a <literal>FILTER</literal> clause is present, only those rows matching it
are included.
When <literal>GROUP BY</literal> is present, it is not valid for
are included in the input to that aggregate function.
</para>
<para>
When <literal>GROUP BY</literal> is present,
or any aggregate functions are present, it is not valid for
the <command>SELECT</command> list expressions to refer to
ungrouped columns except within aggregate functions or if the
ungrouped columns except within aggregate functions or when the
ungrouped column is functionally dependent on the grouped columns,
since there would otherwise be more than one possible value to
return for an ungrouped column. A functional dependency exists if
@@ -655,6 +662,14 @@ GROUP BY <replaceable class="parameter">expression</replaceable> [, ...]
the table containing the ungrouped column.
</para>
<para>
Keep in mind that all aggregate functions are evaluated before
evaluating any <quote>scalar</> expressions in the <literal>HAVING</>
clause or <literal>SELECT</> list. This means that, for example,
a <literal>CASE</> expression cannot be used to skip evaluation of
an aggregate function; see <xref linkend="syntax-express-eval">.
</para>
<para>
Currently, <literal>FOR NO KEY UPDATE</>, <literal>FOR UPDATE</>,
<literal>FOR SHARE</> and <literal>FOR KEY SHARE</> cannot be
@@ -683,7 +698,8 @@ HAVING <replaceable class="parameter">condition</replaceable>
created by <literal>GROUP BY</literal>. Each column referenced in
<replaceable class="parameter">condition</replaceable> must
unambiguously reference a grouping column, unless the reference
appears within an aggregate function.
appears within an aggregate function or the ungrouped column is
functionally dependent on the grouping columns.
</para>
<para>