2 months ago
My PostgreSQL service in Railway shows a 50 GB volume mounted at /var/lib/postgresql/data in the UI.
But inside the container, df -h still shows:
/dev/zd23008 434M 420M 4.1M 100% /var/lib/postgresql/data
Postgres crashes with:
FATAL: could not write to file "pg_wal/xlogtemp.*": No space left on device
I already resized the volume and restarted/redeployed the service, but the mounted filesystem inside the container remains 434 MB.
This looks like the UI volume size and the actual attached filesystem/device are inconsistent.
Can you check whether the resize failed to apply or whether the wrong volume/device is attached to the service?
4 Replies
2 months ago
Hey, is the issue still present if you attempt to resize the volume to an even higher capacity (such as 75GB)?
2 months ago
Yes
2 months ago
We can confirm this is a platform-side issue. Your volume resize to 50 GB was recorded, but the underlying filesystem was not expanded to match, which is why the container still sees only 434 MB. This requires manual intervention from our infrastructure team to resolve. We're escalating this now so the filesystem can be corrected.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
Apologies for the delay. We've verified your Postgres service is now running with a correctly sized volume. The original resize issue where the volume size didn't fully propagate has been addressed, and we've shipped a fix to prevent this from happening on future volume resizes.
2 months 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 • about 2 months ago