Commits on Aug 21, 2026
-
Add autovacuum_warning to report concurrent vacuum collisions
Introduce a new GUC, autovacuum_warning (off by default), that logs a message when an autovacuum worker attempts to process a table that is already being vacuumed by another worker. Such collisions are a sign that autovacuum may not be keeping up, so surfacing them helps operators diagnose the situation. This is modeled after checkpoint_warning, which similarly logs when checkpoints occur too frequently. The message carries a generic hint to tune the autovacuum configuration, since a collision has no single root cause and naming one parameter could be misleading. Author: Shinya Kato <shinya11.kato@gmail.com> Reviewed-by: Discussion: https://postgr.es/m/