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! 🙏
9 Replies
You need to contact support thru the troubleshooting tab.
Also have you tried turning off read only mode?
set default_transaction_read_only = 'off';I tried doing that but still the issues exists
Your situation is odd as you are not showing any overages that would cause supabase to put the DB into read only mode. Odd also that the line above is not toggling that setting.
Contact support if you have not.
I tried contacting them but I received no replies from them i believe it is because of the free version i am using
Did you get back a ticket # email at least. Did you mark it at the highest priority level?
Not much we can do for you here as this is a user helping user forum and not regularly monitored by staff.
I got the ticket id So what should I do now ?
You'll have to wait for support. Or another user to come along with an idea. I don't know what would be forcing it on if you are not exceeding any Free limits.
Can you bring in another user to help me out in this or should I buy the supabase subscription??
But like it's 35$ kind a expensive
I don't "bring" users. They notice posts like I do and answer. I honestly doubt another user has an idea for you, but they would have to have some deeper understanding of postgres and what could causes that to stay read only. IF not Supabase locking it.