mirror of
https://github.com/postgres/postgres.git
synced 2025-07-07 00:36:50 +03:00
Prohibit pushing subqueries containing window function calculation to
workers. Allowing window function calculation in workers leads to inconsistent results because if the input row ordering is not fully deterministic, the output of window functions might vary across workers. The fix is to treat them as parallel-restricted. In the passing, improve the coding pattern in max_parallel_hazard_walker so that it has a chain of mutually-exclusive if ... else if ... else if ... else if ... IsA tests. Reported-by: Marko Tiikkaja Bug: 15324 Author: Amit Kapila Reviewed-by: Tom Lane Backpatch-through: 9.6 Discussion: https://postgr.es/m/CAL9smLAnfPJCDUUG4ckX2iznj53V7VSMsYefzZieN93YxTNOcw@mail.gmail.com
This commit is contained in:
@ -1190,12 +1190,26 @@ max_parallel_hazard_walker(Node *node, max_parallel_hazard_context *context)
|
||||
return true;
|
||||
}
|
||||
|
||||
if (IsA(node, NextValueExpr))
|
||||
else if (IsA(node, NextValueExpr))
|
||||
{
|
||||
if (max_parallel_hazard_test(PROPARALLEL_UNSAFE, context))
|
||||
return true;
|
||||
}
|
||||
|
||||
/*
|
||||
* Treat window functions as parallel-restricted because we aren't sure
|
||||
* whether the input row ordering is fully deterministic, and the output
|
||||
* of window functions might vary across workers if not. (In some cases,
|
||||
* like where the window frame orders by a primary key, we could relax
|
||||
* this restriction. But it doesn't currently seem worth expending extra
|
||||
* effort to do so.)
|
||||
*/
|
||||
else if (IsA(node, WindowFunc))
|
||||
{
|
||||
if (max_parallel_hazard_test(PROPARALLEL_RESTRICTED, context))
|
||||
return true;
|
||||
}
|
||||
|
||||
/*
|
||||
* As a notational convenience for callers, look through RestrictInfo.
|
||||
*/
|
||||
|
Reference in New Issue
Block a user