Thread: Tracking maintenance_work_memory flush pressure

My understanding is that if maintenance_work_mem or autovacuum_maintenance_work_mem value is set too low for the amount of work that autovacuum schedules in a duty cycle, the heap & indexes are scanned in multiple passes.

Is there a way to track these multiple passes in the statistics collections? Or some other way to surface the low memory pressure condition for autovacuum that someone could recommend?

Thanks in advance for any assistance anyone can provide,

Joe