MDEV-32575 MSAN / Valgrind errors in test_if_cheaper_ordering upon re… #3762
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.
…aching in_predicate_conversion_threshold
Description
When converting an IN-list to a subquery, a temporary table stores the IN-list values and participates in join optimization. The problem is the bitmap of usable keys for the temporary table is initialized after the optimization phase, during execution. It happens when the table is opened via
ha_heap::open()
, after the subroutineset_keys_for_scanning()
is called. Trying to access the bitmap earlier, during optimization, leads to MSAN/Valgrind errors.This fix removes the dependency on
set_keys_for_scanning()
. The key bitmap is now dynamically composed on demand inkeys_to_use_for_scanning()
, ensuring correctness without imposing strict call-order constraints.Release Notes
When converting a large IN-list of values to a subquery there was a chance that optimizer accessed an uninitialized bitmap of indexes which could lead to wrong results or a crash
Basing the PR against the correct MariaDB version
main
branch.PR quality check