pgsql: Improve documentation about CASE and constant subexpressions. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Improve documentation about CASE and constant subexpressions.
Date
Msg-id E1Y1inF-000469-Ck@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
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.

Branch
------
REL9_0_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/0c54cb0e3a61af18ec8d528eb802dd8fc9f7d4eb

Modified Files
--------------
doc/src/sgml/func.sgml   |   12 +++++++-----
doc/src/sgml/syntax.sgml |   49 ++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 56 insertions(+), 5 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Improve documentation about CASE and constant subexpressions.
Next
From: Tom Lane
Date:
Subject: pgsql: Improve documentation about CASE and constant subexpressions.