diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2014-11-14 17:19:29 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2014-11-14 17:19:42 -0500 |
| commit | df3e23e1b509001ac9336763404406bdcad04dcc (patch) | |
| tree | 75157d396ab6551367865d7ebd217025739c4786 /contrib/postgres_fdw/deparse.c | |
| parent | 2113f7215d2e13f07c277a86efae900b25d94dc1 (diff) | |
| download | postgresql-df3e23e1b509001ac9336763404406bdcad04dcc.tar.gz postgresql-df3e23e1b509001ac9336763404406bdcad04dcc.zip | |
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.
Diffstat (limited to 'contrib/postgres_fdw/deparse.c')
0 files changed, 0 insertions, 0 deletions