postgres migrate data failed to migrate
Was just trying to migrate my postgres db to latest version and the migration failed
37 Replies
Project ID:
d1ff40c5-a9bf-4677-a3e0-f9a1c3d20b81d1ff40c5-a9bf-4677-a3e0-f9a1c3d20b81
Need help ASAP if possible - have live users and concerned about uptime
@Ray - migration still failing
got this
looks like a disk space issue
i do think this db is rather large
youre on hobby?
yes
im down to upgrade if possible
i already spend quite a bit a month
fyi - i dont see an easy way to upgrade my plan as a user
going forward you'd want to be on pro since you likely are not running a hobby workload, but right now we will wait for ray and hopefully he will be able to push the migration along by temp bumping the volume size
i see no button anywhere to upgrade
ty! 🙌
brings you to https://railway.app/new/team
and also here https://railway.app/account/plans
ahh my bad i overlooked it in a hurry
thanks for sharing!
dont have any eta for rays arrival so upgrading to pro may be the faster option if youd like
was just looking at details - does pro plan also include $20 usage per month?
nope 😦
ah i see hmm
i think it may not be feasible for me at current stage to go for pro plan yet
don't get me wrong - i'm super happy customer and endorse railway to all my friends and on twitter too!
i just don't have a need for the higher workloads / more RAM yet given my business
i guess the only constraint i'm facing is the DB disk size for that one project
its not so much about upgrading to get 32 vcpu and 32 gb of mem, its more so based on the workload youre running, if you have users and are generating revenue, then thats generally a pro workload
but in your case youd also be upgrading to get the 50gb volumes
Hey there,
I can help you migrate. It is indeed failing because it is running out of disk space
I can increase the amount of available space in this specific database so that you can get migrated if that works for you
yaa i agree! to be honest the business is still pre-revenue and very early stage. I'm also bootstrapping as well so trying to be as cost-concious as possible.
will definitely reconsider pro plan few months down the line if business is going well and team grows too 😊
I will increase to 50GB in the meantime
thanks for the quick response! that would be helpful 🙂
np! You should be able to run the migration again!
running again
ah I see it failed again. This problem is that some data had already been migrated to the new DB. Do you mind deleting the v2 "Postgre" service (the one with the volume) and rerunning the migration from the start
ahh i see
it will give it a fresh db
that I will also increase the volume size on
(Don't delete the legacy plugin)
I'm happy to do this as well if you would like. But I won't touch your project without your go ahead
any risk of data loss?
Nope. Not if you just delete this https://railway.app/project/d1ff40c5-a9bf-4677-a3e0-f9a1c3d20b81/service/89f146af-69da-4ea2-9ed7-d6f2bde6918a
All the data is still in "Postgres Legacy"
ahh ok
done
deleted it
Cool. And now can run the migration again. Also feel free to remove the services that have crashed
Updated the new database to 50gb
awesome, running again and will remove the crashed onces
nice! Your service is pointed to the new database too
awesomeee just checked 🙂 everythings working now
will delete the old plugin
thanks again for your help!
glad I could help 😄 Sorry again for the hicuups