Databases randomly crashing
I have two databases in two different projects with different issues:
1- i migrated a database with the migration tool, it worked without a hitch untill i changed up some variables. after that it started crashing every time after it redeploys. The issues is i rolled back to a previous version and it works fine (with the new variables supposedly)
2- I tried cloning my current DB in PG on my other project, but it went above the 5GB limit, now it crashed on every redeploy and i have no way to fix it
Solution:Jump to solution
1. did you change variables on the database service itself?
2. this would require upgrading to pro, then you can grow the volume to 50gb...
44 Replies
Project ID:
9a030c03-e00f-480e-b149-57c0b8f58bb39a030c03-e00f-480e-b149-57c0b8f58bb3
e40da83a-cffa-4c89-a560-e1b51f20a45c
Solution
1. did you change variables on the database service itself?
2. this would require upgrading to pro, then you can grow the volume to 50gb
1 - yes
2 - i wish i could just spin my db back up and rollback my change, i wanted to clone and delete, i am far from using the 5Gig with my one DB. no need for 50gb
1. what was changed?
2. unfortunately without the needed disk space it won't be possible
1. db name, db password and stuff, but the correct ones that still work for connection to the DB currently
2. well that's dumb ? i exceeded the max space shouldn't make my DB unavailable unless i pay more for what i don't need. especially that it was a mistake
1. Those are variables used to initialize the database, changing them does nothing but cause issues
2. thats um how storage works though?
1. doesn't make much sense, it should be idempotent. i corrected the variables and the database exists with those same ones it should just work again.
2. i understand, i am looking for a way for railway to assist me to fix this
1. thats just how postgres itself works, its just a postgres docker image, nothing fancy
2. upgrading to pro would be the only way for you to grow the disk, unfortunately railway cant increase plan limits for hobby users
1- im saying that changing the variables shouldn’t technically break the image
2- I don’t want my storage increased. I want to access my database to delete the excess data I added by mistake.
don’t mean yo be rude but please you’re basically telling me that i’m stuck with this easily fixable problem just “because”, you’re not offering any help. and paying more to go back to using less than 5gb data isn’t a solution
do you still have the database that you changed variables on?
yes
set the variables back to what they originally where
it’s working after i rolled it back, but if i change the variables to anything and it rebuilds it breaks
and idk why i have the correct variable
and i dont remember the exact ones i had before
roll the database back to when it works, dump the database, and restore it to a new database
that is a solution i wanted to keep as last resort, seems like much work for something that shouldn’t happen, but fair
can anyone still railway support help with my other issue though :’)
whats the other issue?
the database with excess data that doesn’t launch anymore
railway can't increase limits for hobby users
then again, thats not at all what i’m asking
has the database used its 5gb volume up?
man, yes. i want to connect back to it to delete the extra data
it will therefore use LESS than 5gb
its ran out of disk space, it cant start without more disk space
and why would it crash just because it is above 5gb
because its a 5gb volume, thats the limit
i assumed, and since there could exist a simple solution to this, i am seeking that help
if you need more disk space then a plan upgrade is required
maybe they can temporarily enable/access/rollback the db idk
saying : just upgrade is very unhelpful
im sorry but they can't increase limits for hobby users, and rolling back is not something they can do either
im sorry thats the solution is not one that you are particular fond of, but its the only way to get an increased volume size as a hobby user
that is not a direct solution to the issue, and a platform like railway should have (and probably does) a simple solution for issues like these
if you where pro, yes, but as a hobby user they cant increase limits
man, please i dont want my limits increased
your database needs a bigger volume to start back up, aka a limit increase, im not sure where the confusing is coming from
ok imagine this, you’re and engineer at railway, you have unlimited access to everything. you could turn a dial and allow a user (or yourself) to access a db TEMPORARILY, fix a size limit and you know… the user keeps using his hobby plan
and it would take no effort and 3 minutes
is that hard to imagine ?
its not hard to imagine at all, they can turn any dial they want, but it is against policy to do this for hobby users, that is why its not something they will do, please understand this
i am a paying user with a small issue, i am not asking for preferential treatment and a free upgrade
so yes i understand what you are saying but it makes little sense to me
hobby users dont get team support either
well then that’s a whole other issue
could’ve started with that
i dont see issue with that personally, if there was an issue with the platform itself you could get team support, but this isnt a platform issue
i could argue that a user who accidentally (or not) hits his disk cap shouldn’t lose access to functionality and have a way to get back below that cap. And that would be a platform issue
you would be 100% correct if these databases where managed databases, but they are fully unmanaged, thus railway is not responsible for anything that happens to them via the user
can you downgrade the pro plan after upgrading to it then ? ^^
yeah
thanks