-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(db): Delete recipients without sub query #9761
Merged
Merged
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
|
ChristophWurst
changed the title
fix(db): Delete recipients with JOIN, not subquery
fix(db): Delete recipients without sub query
Jun 20, 2024
MySQL does not use indexes for the "dependent" subquery. It's either a bug or a missing optimization. EXPLAIN for the two queries is fine in isolation but when you DELETE with subquery neither the inner nor the outher query use an index. This causes a full table scan on very large tables. Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
ChristophWurst
force-pushed
the
fix/db/delete-recipients-with-join
branch
from
June 20, 2024 12:17
1b0ad10
to
2545318
Compare
AndyScherzinger
approved these changes
Jun 20, 2024
Out of curiosity, have you tried something like this? EXPLAIN
DELETE R.*
FROM oc_mail_recipients R, oc_mail_messages M
WHERE
R.message_id = M.id
AND M.mailbox_id = 26
AND uid IN (36923, 10343)
However, I am not sure we can generate such query with DBAL… |
kesselb
approved these changes
Jun 20, 2024
/backport to stable3.7 |
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.
MySQL does not use indexes for the "dependent" subquery. It's either a bug or a missing optimization. EXPLAIN for the two queries is fine in isolation but when you DELETE with subquery neither the inner nor the outher query use an index. This causes a full table scan on very large tables.
Before
After
Fixes #9760