-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
feat(escalating-issues): Create new index on Group for more efficient query #56180
feat(escalating-issues): Create new index on Group for more efficient query #56180
Conversation
Codecov Report
@@ Coverage Diff @@
## master #56180 +/- ##
=======================================
Coverage 78.67% 78.67%
=======================================
Files 5070 5070
Lines 217986 217986
Branches 36897 36897
=======================================
Hits 171502 171502
- Misses 40946 40948 +2
+ Partials 5538 5536 -2
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to remove some of the older indexes? I would ask Hubert. I don't know how much memory or cost these have.
@armenzg I'll follow up with Hubert on that! |
cb4338e
to
abd5570
Compare
This PR has a migration; here is the generated SQL for --
-- Alter index_together for group (8 constraint(s))
--
CREATE INDEX CONCURRENTLY "sentry_groupedmessage_status_substatus_id_e00e92ae_idx" ON "sentry_groupedmessage" ("status", "substatus", "id"); |
abd5570
to
0834595
Compare
This PR has a migration; here is the generated SQL for --
-- Alter index_together for group (8 constraint(s))
--
CREATE INDEX CONCURRENTLY "sentry_groupedmessage_status_substatus_id_e00e92ae_idx" ON "sentry_groupedmessage" ("status", "substatus", "id"); |
PR reverted: b8241ac |
Objective:
Required for #56168