Database volume size
Hi, I've just attempted to move my database from Databases V1 to Databases V2 (manually, since I had problems using the automated solution on other projects... and I need to do it in a way which minimises downtime), and I've hit the 5GB database size limit on DB V2 whilst migrating my data.
Can this 5GB limit be increased on the Hobby plan?
Doubling the amount I'm paying to run my systems on Railway by upgrading to Pro isn't really an option for me at the moment - and I really don't want to have to move off of Railway.
23 Replies
Project ID:
328a5f9d-67a9-4dd3-a605-143a716f788a328a5f9d-67a9-4dd3-a605-143a716f788a
Hobby plan is unfortunately limited to 5GB volume storage per service
perhaps you could split the database up into multiple services or migrate to an external database
It's just quite frustrating that I was previously able to easily fit within Railway's size limits, and this "better" V2 makes what I'm doing no longer possible.
that's understandable
and splitting the database up isn't really an option. The majority of the storage is a single table with a few million records.
Dang, yea I don't see how you could solve this without either upgrading to pro or moving to an external database
Yeah. I'd love to upgrade to Pro, but I'm trying to keep costs low, and Pro would almost double my spending (and if I kept other people having access, even more than double it)
Makes sense
The good news is that most of this data isn't regularly accessed... so I'll undo what I've done so far with migrating and switch to only migrating the newest data.
and figure out a proper solution later today, probably. :/
The most frustrating thing is the DB should only need ~3.5 GB (* according to postgres pg_database_size... but that might not be accurate), but actually copying the data across means it needs to store stuff in TMP files. Maybe I'll be able to move more of the data if I move it in smaller batches.
I'll flag for the team, this is good feedback
Thread has been flagged to Railway team by @aleks.
At the least - I think it would be worth updating Railway's pricing page to reflect this limitation. Currently, Persistent Storage is under "Included in all plans:", with a description which seems like it's not be updated to reflect the title of the card ("Unlimited inbound and 100GB of Outbound network. More if you need it.")
yeah that subtext is completely wrong for the header of persistent storage, I will definitely bring that up to the team, thank you
cc @jr you're probably already aware, but heads up about plan-specific vol limits affecting migration
Hi @sohcah, we can increase the size of your v2 database for you so that you are able to migrate. Do you know what size you need?
Hi,
For this project - I believe 10GB would be enough, but 15GB might be nice so that I've got enough room to run
VACUUM on the table after I've finished migrating (which I can't do without enough free storage space to store the table twice).
I've got other projects which might end up having similar issues when migrating, but in those cases I can probably reduce the database size (or afford to move to Pro for the project) π
Thanks!!No problem. And it is for the "Postgres" database in the project you linked?
We can also increase the volume size in other projects if needed. We are discussing internally on how to consider this volume limit in general. But for now feel free to reach out to us if more size is needed
Yep
Is anything using the database? When I increase its size it there will be some downtime
A few things are running with it, but nothing critical so happy with some downtime
Cool. I'll update it to 20GB now
updated and redeployed. You should be good to go
Cheers. π