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

Missing optimization opportunity in NLJ planning #3000

Open
hatyo opened this issue Dec 12, 2024 · 0 comments
Open

Missing optimization opportunity in NLJ planning #3000

hatyo opened this issue Dec 12, 2024 · 0 comments
Labels
planner Related to the query planner

Comments

@hatyo
Copy link
Contributor

hatyo commented Dec 12, 2024

When planning a query that involves a join that looks like this:

select id, parent
from s, t
where s.parent = t.id

assuming that we have a value index on t defined as id, parent, that index will not be used, although it might be appealing to do so, if the optimizer is capable of flipping the equality, i.e. t.id = s.parent.

@hatyo hatyo added the planner Related to the query planner label Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
planner Related to the query planner
Projects
None yet
Development

No branches or pull requests

1 participant