Repository navigation
Redesign the try_reverse_output to support more cases #19403
Description
Is your feature request related to a problem or challenge?
After #19064 done, i found it can't meet my internal project requirements:
- We can redesign the try_reverse_output to use eq_properties
- We will change to use ordering_satisfy because it can handle the following cases:
// - Normalizes both orderings (removes constants)
// - Checks monotonic functions
// - Handles prefix matchingDescribe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
Activity
Nithurshen commentedon Dec 22, 2025
Hi @zhuqi-lucas , I have opened a PR to address this issue.
I implemented the logic in
PushdownSortto utilizeEquivalenceProperties. The optimizer now detects if a column in the sort prefix is constant and strips it from therequired_orderingbefore attempting the pushdown.I've also added a unit test using a mock plan to verify that the
SortExecis correctly removed when the prefix is constant.Kindly let me know what you think.
zhuqi-lucas commentedon Dec 22, 2025
Hi @Nithurshen , sorry i already had a PR, and i will redesign the logic here, and it's not limited to prefix removal, but also monotonic, etc. Also i will update my slt cases.
Nithurshen commentedon Dec 22, 2025
@zhuqi-lucas, No problem.
I will close mine.
[-]Support sort prefix removal when it's logical_constants.[/-][+]Redesign the try_reverse_output to support more cases[/+]Redesign the try_reverse_output to support more cases (#19446)