This repository was archived by the owner on Nov 4, 2024. It is now read-only.
Create index for id_contact and prop_type on rainloop_ab_properties #1588
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
RainLoop does a lot of SQL queries like
SELECT id_prop, id_contact, prop_type, prop_value FROM rainloop_ab_properties WHERE prop_type IN (30,15,16,18) AND id_contact IN (173812,757514);which takes a lot of time if therainloop_ab_propertiesis big (quite noticeable with ~6 million rows).Use this to create index on an existing table:
CREATE INDEX id_contact_prop_type_rainloop_ab_properties_index ON rainloop_ab_properties(id_contact, prop_type);