projects / users / rhaas / postgres.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 80eacaa) | patch
Document evaluation-order considerations for aggregate functions.
authorTom Lane <tgl@sss.pgh.pa.us>
Fri, 14 Nov 2014 22:19:29 +0000 (17:19 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Fri, 14 Nov 2014 22:19:56 +0000 (17:19 -0500)
commit0ce627d465f534a3234750a5b398664dfece4102
tree78de5e3f15653fa609e25f8bba9676e36c90efcftree
parent80eacaa3cdcd10383c333f6f4625af8cee1f7beecommit | diff
Document evaluation-order considerations for aggregate functions.

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.
doc/src/sgml/ref/select.sgml diff | blob | blame | history
doc/src/sgml/syntax.sgml diff | blob | blame | history
Robert Haas's development tree.