Hi Railway team,

My Postgres service is stuck in crash-recovery loop after the volume became full.

- I resized the postgres-volume to 40 GB (Pro plan) to recover from disk full.

- But Postgres still fails with:

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

- WAL recovery starts but cannot complete because the ext4 filesystem was not expanded (still shows very small size while the block device is now ~40GB).

I only increased it to 40GB temporarily because I believe 10GB would have been enough for my needs.

I want to keep costs as low as possible after recovery.

Data is very important (n8n workflows inside - not exported yet).

Please help expand the filesystem from your end (resize2fs) so Postgres can finish recovery.

Logs from Postgres attached below.

Thank you!