Skip to content
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

Backport manual indexes #8235

Merged
merged 2 commits into from Jun 7, 2021
Merged

Backport manual indexes #8235

merged 2 commits into from Jun 7, 2021

Conversation

ericholscher
Copy link
Member

These indexes were on the .org, but not the .com.
We hit some performance issues around this,
so I checked to see which indexes we had and backported them into Django to standardize them.

These indexes were on the .org, but not the .com.
We hit some performance issues around this,
so I checked to see which indexes we had and backported them into Django to standardize them.
@ericholscher ericholscher requested a review from a team June 4, 2021 00:24
Copy link
Member

@humitos humitos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we create these indexes manually to do it CONCURRENTLY and avoid killing the db?

readthedocs/builds/models.py Show resolved Hide resolved
@ericholscher
Copy link
Member Author

Should we create these indexes manually to do it CONCURRENTLY and avoid killing the db?

I don't think these will cause much load -- they are already on .org, and only need to be added to .com.

@ericholscher ericholscher merged commit d7ef5f8 into master Jun 7, 2021
@ericholscher ericholscher deleted the standardize-indexes branch June 7, 2021 21:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants