All we need is an easy explanation of the problem, so here it is.
I’m running PostgreSQL 10 on AWS for a couple years in production and wondering if it’s worth the downtime to perform a VACUUM FULL on the database.
How to solve :
I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.
Method 1
Normally you never have to run VACUUM (FULL). It is only necessary if the tables have become unduly bloated, either because of autovacuum being too slow or because of mass updates.
I would examine the tables you suspect to be bloated with pgstattuple to see how big free_percent is.
20% bloat is normal. Consider VACUUM (FULL) only if you have much more bloat.
Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0