-
Notifications
You must be signed in to change notification settings - Fork 828
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
Missing index for username and identity_zone on users table (Postgres) #1713
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/180190790 The labels on this github issue will be updated when the story is started. |
@torsten-sap since this seemed to be related to dca40d9 |
Yes, we should also check the third one. In the best case changing the order of the recently created index might also solve the others. |
@torsten-sap I verified with a colleague in a larger DB that existing index from solves also this. |
Finding from productive CF UAA showed that there are situations where the existing index is not hit. The proposed index improved the situation significantly. Thus, reopening the issue. |
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/180664577 The labels on this github issue will be updated when the story is started. |
Affected queries:
|
Command for index creation: |
@torsten-sap thanks, so can you please create PR for that |
What version of UAA are you running?
75.9.0
How are you deploying the UAA?
I am deploying the UAA
What did you do?
Executed a SQL manually because we had a postgres issue in bigger landscapes
Example:
You may execute explain analyze.
What did you expect to see? What goal are you trying to achieve with the UAA?
Expected is an indexed scan in the query plan to ensure that we run with the index.
What did you see instead?
Sequenced scan is done because we have no lower index on idz and origin.
Reason found in git log
Second query that way adapted in the following commit: dca40d9
The text was updated successfully, but these errors were encountered: