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

DGI9-584: Feature/pgsql locking #153

Merged
merged 16 commits into from
Dec 19, 2024
Merged

DGI9-584: Feature/pgsql locking #153

merged 16 commits into from
Dec 19, 2024

Conversation

adam-vessey
Copy link
Contributor

No description provided.

@adam-vessey adam-vessey added the minor Added functionality that is backwards compatible. label Nov 21, 2024
`hexdec()` is not quite the "cast" that was desired, directly converting
64 bits to an integer such that negative values could be created.
Instead let's drop to a signed 60 bit integer (using 61 bits).
~2^61 IDs should allow for plenty of space for things to spread out.
If there had been a collision between a "migration" lock and the
control lock, the release of the control lock after acquiring the
migration locks would have lead to the colliding migration lock to
dropped in the pgsql_advisory_locking implementation.
@adam-vessey adam-vessey changed the title Feature/pgsql locking DGI9-584: Feature/pgsql locking Nov 22, 2024
@jordandukart jordandukart marked this pull request as ready for review December 10, 2024 18:57
@adam-vessey
Copy link
Contributor Author

Just for reference: 7f4f4da is addressing https://discoverygarden.atlassian.net/browse/DDST-866

@jordandukart jordandukart merged commit 9ff2c35 into main Dec 19, 2024
1 check passed
@jordandukart jordandukart deleted the feature/pgsql-locking branch December 19, 2024 18:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
minor Added functionality that is backwards compatible.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants