- Services
- Projects
- Resources
- Webinars
- Training
- Case Studies
- Last Mile Delivery App – Massive Postgres Performance Improvement
- SaaS Video Platform – Expert Postgres Troubleshooting
- Middle Eastern Govt – 99.99% Availability Solution
- Fortune 500 – Data Engineering and BI Setup
- FinTech – High Availability Cluster
- Whop – Database Infrastructure Migration
- Ventrata – Migration and Performance Tuning
- Whitepapers
- Postgres Talks
- Blogs
- About Us
- Contact Us
Comments (2)
Alex
Hi!
Do you have a real-world scenario when the following will work?
>> If your database server is running out of disk space and you need to reclaim it fast, VACUUM FULL can help (though it is still not ideal—more on that later).
How do you expect to reclaim a space if VACCUM requires it twice?
Umair Shahid
Yes, we have had customer instances where disk space needed to be reclaimed fast and they were ok with locking the table for a bit of time. VACUUM removes dead tuples and frees up space for the table to re-use. VACUUM FULL on the other hand frees up space completely, enabling the OS to re-use it – hence the hint towards reclaiming disk space quickly.
I am not sure I quite understand what you meant when you said “VACUUM requires it twice”. Perhaps you can elaborate that a bit?