a month ago
Postgres-EwSU in project Limit (f2d3762f-2b6a-44a7-9a22-ba0bcc99a43c), production env 6bd2fc67-41f8-456a-8cc0-189d1ce55d0a.
Volume postgres-volume id 2d6be364-3727-4aa4-a3cb-a18e5b3c5af3, instance vol_o53oiozo0ctgofdu, mounted at /var/lib/postgresql/data.
We updated Size MB from 500 to 5120 and redeployed. Dashboard now shows 5.12 GB. Latest deployment 7767f864-ca2c-4b5e-ba8b-1e96cc9e2a06 is SUCCESS, but runtime logs still say pgbackrest: volume 433 MiB and Postgres cannot finish WAL recovery:
FATAL: could not write to file "pg_wal/xlogtemp.67": No space left on device
Redo completes at 1/B3FFEFA8 then the checkpoint write fails. Same pattern as prior threads where sizeMB updated but resize2fs never ran on the ext4 filesystem.
Please expand the filesystem on this volume so the 5GB allocation is actually usable. Do not wipe or delete the volume. Data is still on disk.
1 Replies
a month ago
The resize from 500 MB to 5120 MB was refused by the platform because the Trial plan caps volumes at 500 MB. The staged change is still sitting unapplied with the error "Max size of 500 MB on current plan." The volume never grew, which is why Postgres has no room for WAL recovery.
To unblock this you would need to upgrade to at least the Hobby plan, which allows volumes up to 5000 MB (5 GB, SI). Note that 5120 MB (5 × 1024) exceeds even the Hobby cap, so you would need to set the target to 5000 MB or below, or upgrade to Pro for up to 1 TB.
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