[fix] Better SQL SELECT instead of a timeout query #4363
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.
This query runs when filtering by files or components with "anywhere on bugpath" option. In this case the following query was generated:
SELECT <columns> FROM reports WHERE reports.id IN (id1, id2, ...);
The ID list at "IN" block can be so huges that it eats up all the memory and times out the query. This ID list is now replaced with a nested select:
SELECT <columns> FROM reports WHERE reports.id IN (SELECT report_id FROM <some tables>);