Re: Track the amount of time waiting due to cost_delay

>> I'm struggling to think of a scenario in which the number of waits would be
>> useful, assuming you already know the amount of time spent waiting. Even
>> if the number of waits is huge, it doesn't tell you much else AFAICT. I'd
>> be much more likely to adjust the cost settings based on the percentage of
>> time spent sleeping.

> This is also how I see it.

I think it may be useful for a user to be able to answer the "average
sleep time" for a vacuum, especially because the vacuum cost
limit and delay can be adjusted on the fly for a running vacuum.

If we only show the total sleep time, the user could make wrong
assumptions about how long each sleep took and they might
assume that all sleep delays for a particular vacuum run have been
uniform in duration, when in-fact they may not have been.

Regards,

Sami