DB quota exceeded while database is under limit — what counts toward DB size?
storageHello,
I’m reaching out regarding the notification indicating that my organization has exceeded its quota (DB Size Exceeded) and that a grace period is active until January 18, 2026.
After reviewing the dashboard (Usage > Database & Storage Size), I can see that the current database usage is 0.389 / 0.5 GB (78%), which appears to be below the Free Plan limit. Because of this, I’m having difficulty understanding what specifically is causing the quota to be exceeded.
Could you please clarify:
- what components are included in the actual database size calculation (indexes, WAL files, system tables, metadata, etc.)
- the exact database size currently measured on your side that triggered the quota exceedance
- whether database cleanup or optimization actions could be sufficient to return below the limit without upgrading the plan
For additional context, this is a SaaS project that is still under active development, and I’m trying to avoid upgrading the plan at this stage if optimization or cleanup could resolve the issue.
This would help me determine whether an upgrade is necessary or if adjustments to the existing database are enough.
Thanks in advance for your help.
I’m reaching out regarding the notification indicating that my organization has exceeded its quota (DB Size Exceeded) and that a grace period is active until January 18, 2026.
After reviewing the dashboard (Usage > Database & Storage Size), I can see that the current database usage is 0.389 / 0.5 GB (78%), which appears to be below the Free Plan limit. Because of this, I’m having difficulty understanding what specifically is causing the quota to be exceeded.
Could you please clarify:
- what components are included in the actual database size calculation (indexes, WAL files, system tables, metadata, etc.)
- the exact database size currently measured on your side that triggered the quota exceedance
- whether database cleanup or optimization actions could be sufficient to return below the limit without upgrading the plan
For additional context, this is a SaaS project that is still under active development, and I’m trying to avoid upgrading the plan at this stage if optimization or cleanup could resolve the issue.
This would help me determine whether an upgrade is necessary or if adjustments to the existing database are enough.
Thanks in advance for your help.
