[CBRD-25542] Problem with partition pruning when using multi-column indexes with IN and range predicates #5689
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…stead of indexptr
Hamkua
changed the title
Hamkua
commented
Dec 17, 2024
beyondykk9
approved these changes
Dec 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
http://jira.cubrid.org/browse/CBRD-25542
Partition pruning does not work correctly in the following cases:
When the WHERE clause includes the following conditions:
An IN condition on the partition key column A
A range condition (e.g., > or <) on column B, which forms the same index as the partition key column A, without an equality condition on column B
Additionally, if the partitioned table has an index consisting of columns A, B, and others, and this index is used to scan the partitioned table.
The issue is caused by the use of a multi-column index.
With the addition of the MVCC feature, the
where_rangenow contains aPRED_EXPRthat compares a single column of the index. This has been modified to utilizewhere_rangefor partition pruning.