Run PG migrations in separate transactions#5199
Open
brendanlong wants to merge 1 commit into
Open
Conversation
Some migrations have to happen in different transactions, like adding enums and then using them. This makes every migration run in its own transaction, allowing them each to be atomic. Fixes drizzle-team#3249 Fixes drizzle-team#3466
|
We hit this exact issue (schema created in migration N not visible to migration N+1) and confirmed the fix works |
|
We’re currently experiencing the exact same issue, which is quite annoying. |
|
Would be great if this could get merged. Using enums with postgres + drizzle migrations is a big pain until this is fixed. |
This was referenced Jul 11, 2026
Merged
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
4 participants
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.
Some migrations have to happen in different transactions, like adding enums and then using them.
This makes every migration run in its own transaction, allowing them each to be atomic.
Fixes #3249
Fixes #3466