Thread

Re: Displaying accumulated autovacuum cost

Greg Smith <greg@2ndquadrant.com> — 2011-08-28T09:54:53Z

Updated patch cleans up two diff mistakes made when backing out the 
progress report feature.  The tip-off I screwed up should have been the 
absurdly high write rate shown.  The usleep was accidentally deleted, so 
it was running without cost limits even applying.  Here's a good one 
instead:

LOG:  automatic vacuum of table "pgbench.public.pgbench_accounts": index 
scans: 1
     pages: 0 removed, 163935 remain
     tuples: 2000000 removed, 2928356 remain
     buffer usage: 117393 hits, 123351 misses, 102684 dirtied, 2.168 
MiB/s write rate
     system usage: CPU 2.54s/6.27u sec elapsed 369.99 sec

-- 
Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support  www.2ndQuadrant.us