Vacuum timing in pg_stat_all_tables - Mailing list pgsql-hackers

From Magnus Hagander
Subject Vacuum timing in pg_stat_all_tables
Date
Msg-id CABUevEz9v1ZNToPyD98JnWDGZgG=SmPZKkSNzU9hXQ-nGTQF0g@mail.gmail.com
Whole thread Raw
Responses Re: Vacuum timing in pg_stat_all_tables
List pgsql-hackers
In light of bb8dff9995f (add cost delay time to progress views), looking at the output of 30a6ed0ce4b (track per-relation time spent on vacuum and analyze), it struck me as a bit unclear of what the time is really showing.

Do we want to do something similar for the table views? Or if not, we should probably at least document the effect of cost based vacuum delay on those timings - as in if they are including it or not (which I do believe they are).

While more stats are always nice :), I think just being clear about it in the docs would perhaps be enough for now? Maybe just appending something along the line of "(including cost based delaying)"?

--

pgsql-hackers by date:

Previous
From: jian he
Date:
Subject: Re: new commitfest transition guidance
Next
From: Andrew Dunstan
Date:
Subject: Re: what's going on with lapwing?