a month ago
Title: PostgreSQL stuck in recovery mode after disk full — volume is 500MB/500MB
Hello everyone,
My PostgreSQL service on Railway is stuck in recovery mode after running out of disk space.
Logs:
PANIC: could not write to file "pg_logical/replorigin_checkpoint.tmp": No space left on device
Now connections return:
FATAL: the database system is in recovery mode
Important details:
- Current volume usage reached around 500 MB / 500 MB
- No backups are available
- The attached volume still exists
- The Evolution API depends on this database
- I want to avoid deleting/recreating the volume because the data may still be recoverable
- The database likely needs temporary free space to complete recovery/checkpoint
- Current volume usage reached ~500 MB / 500 MB
Question:
What is the safest way to recover this PostgreSQL volume on Railway?
Is there any way to temporarily expand/unlock the attached volume, or access the volume to remove unnecessary files/logs so PostgreSQL can finish recovery?
Project: CRM-CREDFACIL
Environment: production
Thank you.
1 Replies
a month ago
Your Postgres volume is at 100% capacity and crash-looping because it cannot write the recovery checkpoint. On the Hobby plan you can resize your volume up to 5 GB. Click the volume attached to your Postgres service, then click "Live Resize" and increase the size (e.g. to 1 GB or more). Because the volume is at 100% capacity, the system will automatically perform an offline resize with data integrity checks, which restarts the service. After the resize completes, PostgreSQL should have enough free space to finish its recovery checkpoint and come back online. Once it is healthy, redeploy your Evolution API service as well.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 27 days ago