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

Secondary indices chooser should take into account limits #10486

Open
ssmike opened this issue Oct 16, 2024 · 0 comments
Open

Secondary indices chooser should take into account limits #10486

ssmike opened this issue Oct 16, 2024 · 0 comments
Assignees

Comments

@ssmike
Copy link
Collaborator

ssmike commented Oct 16, 2024

Example:

SELECT * FROM `Table`
WHERE IndexedColumn = 2
LIMIT 1

Even if there is a secondary index built on IndexedColumn plan with fullscan is done sequentially. Thus it's more optimal. At least in simple cases automatics should choose an alternative with limit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant