MDEV-32083 INSERT..SELECT crashes if target table appears in a derive… #3924
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.
…d table within the SELECT clause
Description
The cause if the problem is an outdated value of
JOIN::tmp_table_param::field_count
after derived table materialization.JOIN::tmp_table_param
is initialized duringcount_field_types()
(join preparation phase). A derived table may be marked as merged at this point, but later it may be forced to materialization. Materialized derived table provides other values forJOIN::tmp_table_param
, so it is necessary to re-calculate them after switch to materializationRelease Notes
How can this PR be tested?
./mtr insert_select
Basing the PR against the correct MariaDB version
main
branch.PR quality check