add LockPostgreSQL and BenchmarkDistLockers #39
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.
Add the following two
LockPostgreSQL
implementsDistLocker
using advisory locks in PostgreSQLBenchmarkDistLockers
to compare the performance for distributed lockersIt will be easier to review in unified view and hide whitespace.
I should reopen the previous PR instead of creating a new one. Anyway, the difference is that in #38 I used session-level advisory lock. Since in the test we share the same database connection, thus the same session, between two lockers, they interfere with each other as the lock acquired by one locker can be released by the other one. In this PR I use transaction-level advisory lock, so each locker has its own transaction even if they share the same database connection.