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

DO NOT MERGE [RND-643] Investigate Serializable Snapshot Isolation (SSI) in PostgreSQL #308

Closed
wants to merge 5 commits into from

Conversation

jleiva-gap
Copy link
Contributor

  • Add retry logic to upsert, update and delete.
  • Update transactions to use SSI.
  • Add validation to retry, when error code: 40001.
  • Add the POSTGRES_MAX_NUMBER_OF_RETRIES to env file. Add tests to validate changes.
  • Remove FOR SHARE NOWAIT from select

Description

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • I have signed all of the commits on this PR.
  • I have agreed to the Ed-Fi Individual Contributors' License
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

…eSQL

Add retry logic to upsert, update and delete.
Update transactions to use SSI.
Add validation to retry, when error code: 40001.
Add the POSTGRES_MAX_NUMBER_OF_RETRIES to env file.
Add tests to validate changes.
Remove  FOR SHARE NOWAIT from select
@jleiva-gap jleiva-gap changed the title [RND-643] Investigate Serializable Snapshot Isolation (SSI) in PostgreSQL DO NOT MERGE [RND-643] Investigate Serializable Snapshot Isolation (SSI) in PostgreSQL Oct 17, 2023
@jleiva-gap
Copy link
Contributor Author

With the change some of the tests are generating deadlocks and must be addressed. The results were documented in the main repository

@jleiva-gap jleiva-gap closed this Oct 17, 2023
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.

1 participant