[SERVER-55654] Optimize non-removable, range-based windows Created: 30/Mar/21 Updated: 06/Dec/22 Resolved: 21/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Percy | Assignee: | Backlog - Query Optimization |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Query Optimization
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
WindowFunctionExecRange handles all range-based windows the same way: each step, it finds the window's endpoints. For a left-unbounded window like [unbounded, +3], we can make a couple improvements:
|
| Comments |
| Comment by David Percy [ 21/Apr/21 ] |
|
We ended up doing this in the same commit as |