Technical details behind "running low on disk" notification for Postgresql service

Posted August 10, 2020 370 views
DigitalOcean Managed PostgreSQL Database

I have 2 databases in my service plan and their size is less than 8GB (4300MB + 3000MB)
I have been seeing “running low on disk” notifications starting 2 weeks ago even though their size were even less the 8GB ( more then 2 GB to 10GB limit).

Those are the sizes I can see from pgadmin.
What is the reason I was seeing those notifications and why my databases went to readonly even though I still have 2GB?


These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
2 answers

Hi there @metehanr,

I believe that as you are going under 20% of available disk usage, that’s why you are getting the notifications.

What I could suggest is double-checking your overall disk usage to make sure that this is indeed the case. To do so for your managed database cluster follow these steps:

  • Go to your control panel at
  • Then go to your managed database instance
  • Click on ‘Insights’ then from the dropdown choose the name of your cluster
  • There you would be able to see all kinds of different metrics including your disk usage.

Managed database usage


Hi @bobbyiliev ,

When I check pgadmin I see total databases size around 5GB (after I removed data from test database)
Therefore disk usage should be around %50.
But What I see on Insight tab almost %70.
Either what pgadmin shows is wrong or how you calculate is different.
In any case it is misleading.
My database went to readonly what I believed I had 2GB more disk.

Could you clarify the differences and why I cannot use whole 10GB disk size, what I thought I payed for.

dodb (8305 kB)
defaultdb (8281 kB)
x (5084 MB)
dev (45 MB)
template1 (8289 kB)