util: Add indices for queue history tables to gather statistics #1946
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
4ee1370 to
66eadbc
Compare
66eadbc to
3dba768
Compare
pierre
approved these changes
Jan 13, 2024
| PRIMARY KEY(record_id) | ||
| ) /*! CHARACTER SET utf8 COLLATE utf8_bin */; | ||
| CREATE INDEX notifications_history_tenant_account_record_id ON notifications_history(search_key2, search_key1); | ||
| CREATE INDEX notifications_history_effective_date ON notifications_history (effective_date); |
Member
There was a problem hiding this comment.
Nit: extra space after table name (same in migration file)
reshmabidikar
approved these changes
Jan 15, 2024
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.
No description provided.