My Postgres volume (postgres-volume, ID: a075837d-829d-4e06-84b6-0fb00027d64d) was at ~460MB/500MB when a large DELETE operation generated WAL files that filled the remaining space. Postgres crashed and cannot recover.                        

I resized the volume from 500MB to 5GB via the dashboard, and redeployed multiple times, but Postgres still fails with the same error:                                                                                                                                    

FATAL: could not write to file "pg_wal/xlogtemp.30": No space left on device     railway volume list shows 460MB/5000MB (5GB allocated, only 460MB used), so there should be plenty of free space. It appears the ext4 filesystem inside the volume was not expanded to match the new 5GB block device size.

I also tried detaching and reattaching the volume, then redeploying — same result.

  Project: polycopy-backend

  Environment: production

  Volume ID: a075837d-829d-4e06-84b6-0fb00027d64d

  Service: Postgres (ghcr.io/railwayapp-templates/postgres-ssl:17.7)

  Region: europe-west4-drams3a

Could you please run resize2fs (or equivalent) on the volume's block device so the filesystem expands to the full 5GB? This is blocking all database operations.