]> granicus.if.org Git - postgresql/commit
projects / postgresql / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 2113f72) | 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:42 +0000 (17:19 -0500)
commitdf3e23e1b509001ac9336763404406bdcad04dcc
tree75157d396ab6551367865d7ebd217025739c4786tree | snapshot
parent2113f7215d2e13f07c277a86efae900b25d94dc1commit | 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 | history
doc/src/sgml/syntax.sgml diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.