-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
sql: improve tuple index spans #6390
Comments
The prefix thing appears to be fixed, although I'm not sure when or how:
|
I think the prefix thing was the other way around - having an index on |
Support for tuple inequalities like `(a, b, c) > (1, 2, 3)`. This code is more functional than the legacy index constraints code: - we support restricting the inequalities to a prefix, e.g. `(a, b, c) > (1, 2, 3) -> (a, b) >= (1, 2)` (cockroachdb#6390). - we correctly handle cases like `(a, b) BETWEEN (1, 2) AND (3, 4))` (cockroachdb#20504). Minor changes to opt test: support `asc/desc` and switch the order of `legacy-normalize` and `build-scalar` in tests (we don't want to build a scalar before doing the normalization). Release note: None
Support for tuple inequalities like `(a, b, c) > (1, 2, 3)`. This code is more functional than the legacy index constraints code: - we support restricting the inequalities to a prefix, e.g. `(a, b, c) > (1, 2, 3) -> (a, b) >= (1, 2)` (cockroachdb#6390). - we correctly handle cases like `(a, b) BETWEEN (1, 2) AND (3, 4))` (cockroachdb#20504). Minor changes to opt test: support `asc/desc` and switch the order of `legacy-normalize` and `build-scalar` in tests (we don't want to build a scalar before doing the normalization). Release note: None
Regarding the second bullet point: if we have |
Fixes cockroachdb#6390. Release note: None
Things missing from the current tuple index selection code:
cockroach/sql/index_selection.go
Line 573 in 69c632d
cockroach/sql/index_selection.go
Line 586 in 69c632d
cockroach/sql/index_selection_test.go
Line 531 in c7d6b66
The text was updated successfully, but these errors were encountered: