Repository navigation
fix(migrate): drop session advisory lock (0.1.6) - #7
Merged
Merged
Conversation
Found adopting moshcoding.com: through a pool (libsql-pg, postgres.js max>1) pg_advisory_lock and unlock can run on different connections and leave the lock held, hanging the next migrate. Statements are idempotent and the concurrent-create race retries on 'already exists'. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Found adopting moshcoding.com: through a pool, pg_advisory_lock/unlock can hit different connections and leave the lock held. migrate() now relies on idempotent DDL and retries the concurrent-create race. 86 tests incl. concurrent migrate on Postgres and libsql-pg.
🤖 Generated with Claude Code