Hey there! We've found the following might help you get unblocked faster:

• 🧵 Postgres crashed: need help removing [postmaster.pid](postmaster.pid)

• 🧵 Disk usage discrepancy

• 🧵 Recurring Timeout Issues on n8n Server - Postgres Checkpoint Blocking System

• 🧵 URGENT: Database crashed - No space left on device - Production down

If you find the answer from one of these, please let us know by solving the thread!

It is not completely normal to take 1 Gb before you give me this reply.

I started with a lower size as well, so there should be memory and disk cleanups going on to reduce the overall size. If my database is 73 mb. Considering walsize was 1 gb earlier it was acceptable for the total size to be 1gb, now I changed it to 256mb, so the overall size should also reduce

Hey, I believe that this is a combination of the file system overhead, plus Postgres not freeing the space automatically when deleting records (altering schema). You can run VACUUM FULL;, but chances are, that it won't decrease the space by a lot, or not at all, as your WAL will increase.

With that being said, you can always deploy a new database, migrate the data over and delete the old one. I also deployed a new Postgres database on the pro plan with the volume size of 50GB (default of the pro plan) and it seems to be using 1GB of disk without anything in the database, meaning that most of it are part of the file system overhead.

already did VACUUM and I removed indexes not needed and reduced wal size. Ig it just needed some time to relax it's back to 540mb which I expect the db to be around.

If you are getting 1 gb consider reducing wal size

It says bounty awarded, who did you award the bounty too?

It was awarded to no one as you solved it yourself (the message with the green background is the solution and it is your own message above). The bounty awarded label in this case is just to mark this thread as solved.