<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vacuum on Percona Community</title><link>https://percona.community/tags/vacuum/</link><description>Recent content in Vacuum on Percona Community</description><generator>Hugo 0.147.5</generator><language>en-us</language><lastBuildDate>Wed, 01 Jul 2026 11:00:00 +0000</lastBuildDate><atom:link href="https://percona.community/tags/vacuum/index.xml" rel="self" type="application/rss+xml"/><item><title>PostgreSQL Autovacuum Internals and Benchmark</title><link>https://percona.community/blog/2026/07/01/postgresql-autovacuum-internals-benchmark/</link><pubDate>Wed, 01 Jul 2026 11:00:00 +0000</pubDate><guid isPermaLink="true">https://percona.community/blog/2026/07/01/postgresql-autovacuum-internals-benchmark/</guid><description>&lt;p>Vacuum, or more precisely autovacuum, is the most important automatic maintenance task in PostgreSQL. It is key for performance, but also for long-term database survival. If it runs too often, it can damage performance. If it does not run often enough, performance can suffer. With too few workers, it takes too long. With too many, it consumes resources. If the maintenance work memory is not enough, the load can multiply due to multiple index scans. If you disable it completely, it will rise from the dead and run without limits.&lt;/p></description></item></channel></rss>