-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: simplify migration script #2674
Conversation
You can find the image built from this PR at
Built from 98f38f5 |
You can find the image built from this PR at
Built from 98f38f5 |
This reverts commit 740bed9.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ufff so much better. Thanks so much! 🤩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
The meta field is initialized as null in this case?
Thanks for the comments guys! |
1 similar comment
Thanks for the comments guys! |
Description
While running migration scripts we noticed that is better to try to change the table schema directly in the
messages
table. The reason is that is not possible to keep handle a table backup when themessage
table occupies 45GiB and the max size allowed in 50GiBWith this PR we try to allow database migration with low disk availability constraints.
We want to avoid errors like: