Adding the correct indexes for the user table #588
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.
This migration drastically improves the performance of our SQL query because the basic user fetch now takes < 1ms from ~50-60ms on gehirneimer.de
We already have indexes on the user table, however those are all lower(...) ones and we basically never query for
x = lower(...)
so these are basically never used. We do have unique indexes which do the same job, only for default queries, however the one forap_profile_id
was missing and the other ones cryptically named. This PR fixes that