Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

optimize a query only once when binding exists #26002

Closed
Tracked by #25970
eurekaka opened this issue Jul 6, 2021 · 0 comments · Fixed by #26141
Closed
Tracked by #25970

optimize a query only once when binding exists #26002

eurekaka opened this issue Jul 6, 2021 · 0 comments · Fixed by #26141
Assignees
Labels
epic/sql-plan-management sig/planner SIG: Planner type/enhancement The issue or PR belongs to an enhancement.

Comments

@eurekaka
Copy link
Contributor

eurekaka commented Jul 6, 2021

Enhancement

Currently, we would optimize a query firstly, and build a hint from the plan, then check if the hint matches any binding in the cache, if not, we use the bindings for another round of optimize. This would make a query be optimized several times if the hint in the binding is not normalized, and if the query contains uncorrelated subqueries, this optimization process would consume a lot of time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic/sql-plan-management sig/planner SIG: Planner type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant