Propagate query plan optimizations to correlated subquery input#85455
Propagate query plan optimizations to correlated subquery input#85455
Conversation
|
Workflow [PR], commit [7728c54] Summary: ⏳
|
KochetovNicolai
left a comment
There was a problem hiding this comment.
Overall good.
I would prefer creating intermediate steps like dependent join + reference first, and after convert to buffering steps.
Technically, in this case (later) we can swap join sides togther with dependent join refernece steps.
|
Will it only work for correlated subqueries for now? Will it be possible to extend it to more CTEs? |
This PR aims to support only the case of correlated subqueries, but it'll be easy to extend it to CTEs in the future (I have such plans in mind) |
Cherry pick #85455 to 25.10: Propagate query plan optimizations to correlated subquery input
…lated subquery input
Backport #85455 to 25.10: Propagate query plan optimizations to correlated subquery input
|
@novikd Hi, |
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):
Make query plan optimizations visible to the correlated subquery input subplan by postponing it's materialization. Part of #79890.
Documentation entry for user-facing changes