Add SQL index to states.event_id #12825
Merged
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.
Description:
The
States.event_id
field referencesEvent.event_id
but until now there was no index on the former. This potentially makesEvent
purging slow (as reported in #12797) because each removed event does aStates
table scan to check that it is not referenced.MySQL users will have this index already, automatically added due to the foreign key. However, because we did not actually write
States.event_id
values until #12580, this index can be useless (ignored due to low cardinality statistics). I tested that the migration code properly removes this automatic index.This index should also make it possible to return and even improve the optimization in #12608.
Related issue (if applicable): fixes #12797
Checklist:
If the code does not interact with devices:
tox
run successfully.