diff options
author | Amit Kapila <akapila@postgresql.org> | 2018-09-14 09:36:30 +0530 |
---|---|---|
committer | Amit Kapila <akapila@postgresql.org> | 2018-09-14 09:36:30 +0530 |
commit | 75f9c4ca5a8047d7a9cfbc7d51a610933d04dc7f (patch) | |
tree | 888a57df088ecaab838f08475d295ace7e30ae67 /src/include/optimizer/planner.h | |
parent | 0ba06e0bfb8cfd24ff17aca92aa72245ddd6c4d7 (diff) | |
download | postgresql-75f9c4ca5a8047d7a9cfbc7d51a610933d04dc7f.tar.gz postgresql-75f9c4ca5a8047d7a9cfbc7d51a610933d04dc7f.zip |
Don't allow LIMIT/OFFSET clause within sub-selects to be pushed to workers.
Allowing sub-select containing LIMIT/OFFSET in workers can lead to
inconsistent results at the top-level as there is no guarantee that the
row order will be fully deterministic. The fix is to prohibit pushing
LIMIT/OFFSET within sub-selects to workers.
Reported-by: Andrew Fletcher
Bug: 15324
Author: Amit Kapila
Reviewed-by: Dilip Kumar
Backpatch-through: 9.6
Discussion: https://postgr.es/m/153417684333.10284.11356259990921828616@wrigleys.postgresql.org
Diffstat (limited to 'src/include/optimizer/planner.h')
-rw-r--r-- | src/include/optimizer/planner.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/src/include/optimizer/planner.h b/src/include/optimizer/planner.h index c090396e139..3e733b34ed9 100644 --- a/src/include/optimizer/planner.h +++ b/src/include/optimizer/planner.h @@ -47,6 +47,8 @@ extern bool is_dummy_plan(Plan *plan); extern RowMarkType select_rowmark_type(RangeTblEntry *rte, LockClauseStrength strength); +extern bool limit_needed(Query *parse); + extern void mark_partial_aggref(Aggref *agg, AggSplit aggsplit); extern Path *get_cheapest_fractional_path(RelOptInfo *rel, |