diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2014-12-18 16:39:01 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2014-12-18 16:39:01 -0500 |
| commit | 3dd740b3e688b807fd95344561d5c89c72ad5945 (patch) | |
| tree | 5c2a53aaf98782800492dbdc13760b89d97f370b /src | |
| parent | d710116c64ba8971fd48a09e54bf4ba9fcb4a6ca (diff) | |
Improve documentation about CASE and constant subexpressions.
The possibility that constant subexpressions of a CASE might be evaluated
at planning time was touched on in 9.17.1 (CASE expressions), but it really
ought to be explained in 4.2.14 (Expression Evaluation Rules) which is the
primary discussion of such topics. Add text and an example there, and
revise the <note> under CASE to link there.
Back-patch to all supported branches, since it's acted like this for a
long time (though 9.2+ is probably worse because of its more aggressive
use of constant-folding via replanning of nominally-prepared statements).
Pre-9.4, also back-patch text added in commit 0ce627d4 about CASE versus
aggregate functions.
Tom Lane and David Johnston, per discussion of bug #12273.
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions