<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vacuum on Ivan Luminaria</title><link>https://ivanluminaria.com/en/tags/vacuum/</link><description>Recent content in Vacuum on Ivan Luminaria</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 24 Mar 2026 08:03:00 +0100</lastBuildDate><atom:link href="https://ivanluminaria.com/en/tags/vacuum/index.xml" rel="self" type="application/rss+xml"/><item><title>VACUUM and autovacuum: why PostgreSQL needs someone to clean up</title><link>https://ivanluminaria.com/en/posts/postgresql/vacuum-autovacuum-postgresql/</link><pubDate>Tue, 24 Mar 2026 08:03:00 +0100</pubDate><guid>https://ivanluminaria.com/en/posts/postgresql/vacuum-autovacuum-postgresql/</guid><description>&lt;p&gt;A couple of years ago I was asked to look at a production PostgreSQL
instance that &amp;ldquo;slows down every week&amp;rdquo;. Always the same pattern: Monday
is fine, Friday is a disaster. Someone restarts the service over the
weekend and the cycle starts again.&lt;/p&gt;
&lt;p&gt;Database around 200 GB. Main tables occupying nearly three times their
actual data size. Queries falling into sequential scans where they
shouldn&amp;rsquo;t have been. Response times climbing day after day.&lt;/p&gt;</description></item></channel></rss>