feat(dashboard): backfill schema_migrations#1913
Merged
Merged
Conversation
filipecabaco
approved these changes
May 26, 2026
|
Coverage is 91.334% — feat-lp-backfill-migrations into main. No base build found for |
|
🎉 This PR is included in version 2.99.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
3 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.
This is a small addition to Tenant Migrations page to unblock some tenants that can't run migrations.
I found a tenant stuck at migration 7 with error:
This error is happening because after applying pgdelta plan the signature of function
realtime.apply_rlshas changed and that old migration can't callcreate or replaceanymore. Instead of checking and fixing every single statement in every single migration to support this kind of situation, it's better to just backfillschema_migrationsand updaterealtime.migrations_ranbecause the database is valid and updated, just the metadata is incorrect at that point.