2 years ago
I am reaching out to seek your guidance regarding a recent incident involving a crash of my Postgres database due to exceeding the 500MB storage quota. Upon investigation, it appears that the root cause may be related to a backup of the fact table that I initiated.
To resolve the issue and restore functionality, I am considering deleting the backup stored on the filesystem to free up space and enable the container to restart. However, before proceeding, I would appreciate clarification on the following points:
Restart vs. Redeploy: Could you please explain the difference between restarting the container and redeploying it? I want to understand how each action would affect my database and its associated settings and variables.
Data and Settings Preservation: In the event of a redeployment, would I risk losing any tables, settings, or variables configured within the database? I want to ensure that all necessary data and configurations are preserved throughout the process.Your insights and guidance on these matters would be greatly appreciated as I work to resolve this issue promptly. Thank you for your attention to this matter.
Warm Regards,
Stephane
ⓘ Deployment information is only viewable by Project members and Railway admins.
2 Replies
2 years ago
A redeploy stops the container and then builds and starts a new container, a restart stops the running service inside the container and starts it again. Neither action would result in data loss in any form unless you have horribly missconfigured something.
You can simply upgrade to the Hobby plan to get access to 5GB volumes, then go into your volume settings to grow it to 5GB, and this too will not result in any data loss unless something was missconfigured.
2 years ago
thank you, I fixed the issue.
Would you please close the ticket.
kind regards
Stephane
Status changed to Solved Railway • almost 2 years ago