WAL
aromacenter
PROOP

17 days ago

Project: mira

Service: mira-db (PostgreSQL)

Environment: production

Problem:

The PostgreSQL database crashed on 2026-08-04 at 07:24:50 UTC with the error:

"FATAL: could not write to file pg_wal/xlogtemp.50: No space left on device"

The volume was expanded from 5GB to 20GB and the service was redeployed, but the crash persists.

WAL corruption has been detected that is beyond automatic recovery.

Request:

Please restore the PostgreSQL database from the most recent backup before the crash.

Thank you.

Solved

1 Replies

Railway
BOT

17 days ago

The volume resize to 20 GB is currently staged but has not been deployed, so the volume is still at its original 5 GB capacity (99.96% full). You can apply the pending resize by clicking Deploy on the staged changes banner at the top of the project canvas. Our databases are unmanaged, so automatic snapshots, WAL recovery, and PITR are not available unless you previously set up volume backups or PITR yourself - we do not perform database restores on your behalf. If you have existing backups, you can restore them from the service's Backups tab; if not, once the volume resize is applied, you can follow our WAL recovery guide to attempt recovery. Going forward, enable volume backups on your stateful services from the Backups tab so you can self-restore if this happens again.


Status changed to Awaiting User Response Railway 17 days ago


Railway
BOT

10 days 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 10 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...