Push expressions through layout plans - #9166
Conversation
Merging this PR will regress 1 benchmark
Warning Please fix the performance issues or acknowledge them on CodSpeed. Performance Changes
Tip Investigate this regression by commenting Comparing Footnotes
|
4dced78 to
7968c7e
Compare
7968c7e to
a9043d5
Compare
a9043d5 to
bda6747
Compare
bda6747 to
042e358
Compare
2028928 to
0134c4b
Compare
0134c4b to
6c41c35
Compare
6c41c35 to
65aad23
Compare
65aad23 to
265f6c2
Compare
265f6c2 to
b121a9e
Compare
b121a9e to
0e24b8f
Compare
50778e9 to
be85e95
Compare
be85e95 to
f1a1d88
Compare
f1a1d88 to
7e3aae3
Compare
7e3aae3 to
8fd3d94
Compare
8fd3d94 to
cba755f
Compare
cba755f to
24825a7
Compare
24825a7 to
9a87561
Compare
Signed-off-by: Joe Isaacs <joe.isaacs@live.co.uk>
9a87561 to
956389d
Compare
Superseded by #9196
The parent-reduction rule framework and all concrete expression-pushdown/plan-optimization rules are now one signed-off commit and one review unit in #9196.
No implementation was removed: the combined #9196 commit has the same Git tree as this PR's previous head. This PR is closed, and #9187 now targets
vortex-plan-rulesdirectly.