Autovacuum Is Running. Is It Actually Working?
October 20–23
Vacuum gets a bad reputation and other RDBMS vendors are quick to point it out as a PostgreSQL flaw - and yet PostgreSQL keeps getting more and more popular, year after year.
Vacuum is a design decision, not an accident - Fast writes now, clean up later.
The problem is not vacuum. The problem is misconfiguration.
But how do you know if your autovacuum config is wrong? And what does "wrong" even look like?
In this talk we take the same workload and change the parameters - and you see exactly what happens. Dead tuples, bloat, table size, vacuum frequency, all measured, all explained. It will also cover what to do when bloat is already there!
More and more developers are managing their own databases - especially on managed services - without a dedicated DBA, so getting this right is no longer just a DBA concern.
