a month ago
URGENT PRODUCTION POSTGRESQL RECOVERY
Project: keen-balance
Environment: production
Postgres Service ID:
2d3a3901-12e2-42ad-9052-e31be41796b3
Existing Volume:
postgres-volume
Volume ID:
e30ab469-8bc0-438f-8ce8-fe9512b057fa
Problem:
The Postgres volume was expanded/provisioned to 5120 MB (5 GB), but the filesystem visible inside the PostgreSQL container still appears to be approximately 433–500 MB.
PostgreSQL is crashing during WAL recovery with:
"No space left on device"
Please complete the filesystem expansion on the EXISTING Postgres volume so the filesystem can use the full 5 GB.
IMPORTANT:
Do NOT delete, detach, recreate, replace, format, reset, migrate, or initialize the existing Postgres volume.
Do NOT delete or modify any existing PostgreSQL databases, tables, users, transactions, balances, or application data.
Please:
- Complete the filesystem expansion.
- Recover PostgreSQL and allow WAL recovery to finish.
- Verify PostgreSQL becomes healthy/online.
- Verify the filesystem actually shows approximately 5 GB.
- Verify postgres.railway.internal DNS/internal networking.
- Verify Ping-pong-offical-app can connect using its existing DATABASE_URL.
- Leave the existing Redis service and Redis volume unchanged.
This is a production data-preservation issue. Please perform only the infrastructure-side filesystem expansion/recovery required.
1 Replies
a month ago
Your Postgres volume (postgres-volume) is provisioned at 500 MB with ~494 MB used, which is why PostgreSQL is running out of space. The volume was never expanded to 5 GB because your workspace is on the Trial plan, which caps volumes at 500 MB. Any resize request above that cap is rejected by validation, so no filesystem expansion is pending or incomplete. To resize the volume you would need to upgrade to at least the Hobby plan (up to 5 GB) or Pro (up to 1 TB), after which you can resize the volume yourself from the service's volume settings.
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 • about 1 month ago