Use database lock to prevent migrations from running concurrently #204
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.
Use Postgres advisory lock when migrating an event store database to ensure only a single migration can run at a time. This protects against running migrations concurrently by mistake.
A database lock is used to ensure only one migration can run at a time, preventing issues with multi-node deployments where the migration is automatically run on startup where two or more nodes starting at the same time may attempt to migrate simultaneously.
Fixes #192.