Index "twilio_sms_delivery_details.session_id" #1277
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.
Story card: https://app.clubhouse.io/simpledotorg/story/1138/add-an-index-to-twilio-sms-delivery-details-table
Because
We have DB and request strain when we fire off reminders and get callbacks from Twilio. We spend most of our time finding the right
TwilioSmsDeliveryDetail
record by session ID.This addresses
This PR indexes that
session_id
column for quick finds.Note: Do we need to run this thing concurrently? Can someone help me verify against a prod-like dataset? ie, how long will this migration take to run in IHCI production?