3 hours ago
Hi,
I'd like to downgrade my project from Pro to Hobby, but I want to check one thing first so I don't break a production database.
Project: pawgo-crawler (environment: production)
I have 1 volume:
postgres-volume-AjjM Postgres 1.6 GB / 50 GB
The Hobby plan lists "Up to 5 GB storage". My actual usage is well under that, but the Postgres volume is provisioned at 50 GB.
2 questions:
Is the 5 GB Hobby limit measured against provisioned size or actual usage? i.e. will the downgrade be blocked or the service disrupted because the volume is provisioned at 50 GB, even though only 1.6 GB is used?
If provisioned size is what matters, can a volume be shrunk in place? If not, what's the supported path, detach/recreate and restore from a backup? Is there downtime, and is there a recommended procedure?
For context, this Postgres serves a live customer-facing site (info.pawgo.fr), so I'd rather confirm the path before starting than discover a constraint mid-downgrade.
Thanks a lot,
Giovanni
1 Replies
3 hours ago
The downgrade is not blocked by your 50 GB volume, your data stays intact, and the service keeps running normally. The Hobby plan's 5 GB cap is enforced only when you request a resize, not against volumes that already exist, so nothing is checked, shrunk, or disrupted during the downgrade. The one consequence is that you will not be able to resize the volume while it sits above 5 GB (and volumes cannot be made smaller on any plan), but the volume remains fully attached, readable, and writable. Volume storage also bills on measured usage, not provisioned size, so your 1.6 GB of actual data is what you pay for.
Status changed to Awaiting User Response Railway • about 3 hours ago
Status changed to Solved giopawgofr • about 3 hours ago