pgsql: Disable WindowAgg inverse transitions when subplans are present - Mailing list pgsql-committers

From David Rowley
Subject pgsql: Disable WindowAgg inverse transitions when subplans are present
Date
Msg-id E1pRQBW-000s3Q-8C@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Disable WindowAgg inverse transitions when subplans are present

When an aggregate function is used as a WindowFunc and a tuple transitions
out of the window frame, we ordinarily try to make use of the aggregate
function's inverse transition function to "unaggregate" the exiting tuple.

This optimization is disabled for various cases, including when the
aggregate contains a volatile function.  In such a case we'd be unable to
ensure that the transition value was calculated to the same value during
transitions and inverse transitions.  Unfortunately, we did this check by
calling contain_volatile_functions() which does not recursively search
SubPlans for volatile functions.  If the aggregate function's arguments or
its FILTER clause contained a subplan with volatile functions then we'd
fail to notice this.

Here we fix this by just disabling the optimization when the WindowFunc
contains any subplans.  Volatile functions are not the only reason that a
subplan may have nonrepeatable results.

Bug: #17777
Reported-by: Anban Company
Discussion: https://postgr.es/m/17777-860b739b6efde977%40postgresql.org
Reviewed-by: Tom Lane
Backpatch-through: 11

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/836c31ba508c154bc4c4ebb6270761586a6df797

Modified Files
--------------
src/backend/executor/nodeWindowAgg.c | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)


pgsql-committers by date:

Previous
From: David Rowley
Date:
Subject: pgsql: Disable WindowAgg inverse transitions when subplans are present
Next
From: David Rowley
Date:
Subject: pgsql: Fix incorrect presorted DISTINCT aggregate if condition