Added postmeta index for meta_key and meta_value to improve lookup query performance.#84
Draft
sun wants to merge 1 commit into
Draft
Added postmeta index for meta_key and meta_value to improve lookup query performance.#84sun wants to merge 1 commit into
sun wants to merge 1 commit into
Conversation
This file contains hidden or 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
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.
Task
Description
meta_valueindex, but it only covers some strange cases in core and contributed plugins that are filtering bymeta_valuecolumn only (e.g. to retrieve all distinct values) or the value is so unique among all meta fields that it doesn't require further filtering by key; e.g., a URL.meta_keyfor a particularmeta_value.meta_valueindex for those, butEXPLAINstates that it still has to go through thousands of rows to reduce them to the given meta key, which is slow.Examples
TODO: Need to find the actual queries that triggered this – for now here's a trivial:
("using where" should ideally say "using index"; the real cases had 4k rows, the new index reduced them to <100)
We can see that MariaDB 10.4+ already has a built-in optimization, which doesn't need the new index, because it's using a second index to filter the first: