Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Prevent multiple migrations starting in parallel
See original GitHub issueIn an environment with multiple instances of the same application, starting applications with the migration logic in the Startup will start multiple migrations that run in parallel. This can lead to race-conditions where one or more migrations may fail as they all have read that they should start migrations to bring the database up to the latest version.
I believe locking the versioninfo table with an exclusive lock may be the answer to this problem as it will prevent other migrations starting if one has already locked the table in its transaction.
In Postgres: LOCK TABLE versioninfo IN ACCESS EXCLUSIVE MODE;
Issue Analytics
- State:
- Created 7 years ago
- Comments:18 (16 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Right, v0.9.7 is out, which should fix this.
Right! That approach works. I’m tidying up the docs and fixing the unit tests, then I’ll get it merged.