And now, we put on our waders and venture into the swamp that is all of the PostgreSQL logging GUCs. PostgreSQL 8.3 is the release in which the server started doing its own housekeeping in...

PostgreSQL 18 splits autovacuum configuration to finally let you tune worker concurrency without restarting.

autovacuum_work_mem sets the maximum memory each autovacuum worker may use for tracking dead tuple identifiers (TIDs) during a vacuum. Default is -1, which means “inherit from...

Autovacuum's most powerful tuning lever: the scale factor that determines when dead tuples trigger a vacuum. On large tables, the 20% default waits too long.

PostgreSQL 18 finally fixes the autovacuum formula that left billion-row tables waiting for 200M dead tuples.

PostgreSQL 13 added insert-triggered autovacuum to solve a critical problem: append-only tables never vacuumed, breaking index-only scans and delaying tuple…

Three autovacuum parameters control how often PostgreSQL vacuums, how hard it works, and how long it pauses.

Prevent MultiXact ID wraparound by controlling when autovacuum freezes old locks.

Raising autovacuum_max_workers above 3 won't speed up vacuum unless you also increase autovacuum_vacuum_cost_limit—the I/O budget is divided among workers, not…

PostgreSQL wraps transaction IDs every two billion transactions—autovacuum_freeze_max_age stops your database from crashing when it does.

Disable autovacuum and PostgreSQL will cheerfully show you every failure mode in its playbook, from table bloat to transaction ID wraparound.

PostgreSQL 19 ships with parallel autovacuum. The new GUC autovacuum_max_parallel_workers caps the cluster-wide pool, and the per-table storage parameter autovacuum_parallel_workers lets you tune...

2025年1月6日，Nathan Bossart提交补丁，允许动态调整autovacuum_max_workers而无需重启服务器。新增参数autovacuum_worker_slots控制启动时的工作槽数量，修改该参数需重启。设置不当会发出警告，现有工作者继续运行，直到数量低于设定值。这一改动增强了自动清理工作的灵活性。