10 days ago
Details:
Project ID: 25e6210f-0079-491f-9de0-247f5bb6fdd2
Service ID: 68f5934a-f071-4545-a4bd-a6f097b24520
Volume ID: 38f97729-35ca-441d-bc93-d1b4c28bbb39
Questions for support:
What is the current backend lifecycle state of the volume? (READY, RESIZING, ERROR, or other?)
Has the filesystem been successfully expanded to 5 GB?
If the volume state is READY, is it safe to redeploy the Postgres service without replacing or wiping the volume data?
The service has been offline for 3+ hours since the resize operation.
Before resizing, PostgreSQL failed with: No space left on device — pg_wal/xlogtemp.50
Please do not wipe, delete, detach, or replace the existing volume.
1 Replies
10 days ago
The volume's backend state is READY and the filesystem has been expanded to 5 GB, with roughly 494 MB currently in use, so the resize completed successfully and your data is intact. The Postgres service is offline because its last deployment was removed, not because of a volume issue. You can safely redeploy the service from its settings, and it will mount the same volume with all existing data preserved.
Status changed to Awaiting User Response Railway • 10 days ago
3 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 • 3 days ago