> I agree that the "processing database" message isn't too exciting, but > it seems that forcing per-table messages up to LOG level would create > even more log clutter. I could support "processing table" at level > DEBUG1 and "processing database" at DEBUG2. Or maybe we should think > harder about the idea recently mentioned of letting the autovacuum > process have its own log-level setting, separate from ordinary backends' > setting. I would be helpful that the message gives the result also, like 23 tables in database 'foo' processed, 45 tables skipped, 12345 dead tuples removed in 45 seconds Andrus.