14 days ago
Postgres in project “skm-n8n”, production environment, has crashed because its 500 MB volume is full. Logs show PANIC/FATAL: could not write to file "pg_wal/xlogtemp.*": No space left on device.
Deleting n8n test execution history also fails because PostgreSQL cannot write WAL. Please help inspect the volume for safely removable temporary files or logs and restore database operation. Preserve workflows, credentials, schemas and configuration. Please confirm any additional charges before making billable changes.
1 Reply
14 days ago
The fastest way to get Postgres writing again is to grow the volume from its settings with Live Resize. Hobby volumes can go up to 5GB, and resizing only adds capacity, so your workflows, credentials, schemas and configuration stay on the same volume. Because this volume has hit 100%, the resize runs offline to check data integrity, which restarts Postgres briefly.
On cost, volumes are billed only for the storage actually used, not the provisioned size. Making the volume bigger does not raise your bill by itself. Charges only grow if your data does. Once Postgres is up, you can delete the old n8n execution history to bring usage back down. Volumes can't be shrunk, though, so the extra capacity stays.
We don't remove files from customer volumes. If you'd rather inspect it yourself first, railway volume browse lets you look through the volume's files. Deleting files under pg_wal by hand can corrupt the database, so resizing is the safer route.
Status changed to Awaiting User Response Railway • 14 days ago
7 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 • 7 days ago