Forced reduced size of database that cause Readonly mode issues
Hey Supabase team! 
I’m facing a read-only database issue that seems to be caused by an incorrect size limit.
Project ref: <PROJECT_REF>
Problem:
Dashboard shows current DB size = 30.89 MB and max DB size = 30.89 MB (same value).
But my plan is the Free plan (0.5 GB limit) and my actual data is only ~16 MB according to pg_database_size().
DB is stuck in read-only mode (SHOW default_transaction_read_only; → on).
What I’ve checked:
No unpaid invoices or billing warnings.
Storage usage = 0 GB.
Tried creating a new project in the same org → same issue.
Why I think it’s wrong:
It looks like my project’s Postgres instance was artificially capped at ~30 MB, even though the free-tier limit is 0.5 GB.
Could someone please check / reset this project’s allocation so it gets the normal 0.5 GB and is writable again?
If transfer to a new org would fix it, please confirm.
(Attaching screenshot + diagnostic info from Lovable.ai showing actual DB = 16 MB but max = 30.89 MB.)
Thanks so much!
I’m facing a read-only database issue that seems to be caused by an incorrect size limit.
Project ref: <PROJECT_REF>
Problem:
Dashboard shows current DB size = 30.89 MB and max DB size = 30.89 MB (same value).
But my plan is the Free plan (0.5 GB limit) and my actual data is only ~16 MB according to pg_database_size().
DB is stuck in read-only mode (SHOW default_transaction_read_only; → on).
What I’ve checked:
No unpaid invoices or billing warnings.
Storage usage = 0 GB.
Tried creating a new project in the same org → same issue.
Why I think it’s wrong:
It looks like my project’s Postgres instance was artificially capped at ~30 MB, even though the free-tier limit is 0.5 GB.
Could someone please check / reset this project’s allocation so it gets the normal 0.5 GB and is writable again?
If transfer to a new org would fix it, please confirm.
(Attaching screenshot + diagnostic info from Lovable.ai showing actual DB = 16 MB but max = 30.89 MB.)
Thanks so much!
