Incremental fixes for lock contention #945
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rkachowski
force-pushed
the
dhutch/drop_address_foreign_keys
branch
from
e49b304
to
defd25e
Compare
This reverts commit 7df9785.
rkachowski
force-pushed
the
dhutch/drop_address_foreign_keys
branch
from
defd25e
to
1dd0425
Compare
rkachowski
changed the title
alvarof2
approved these changes
Sep 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Upstream patches for addressing lock contention, with the exclusion of removing foreign key constraints on tables across the db schema. This was removed due to concerns with reversibility raised during the last data-services review meeting.
Other changes
Tested
Issues