Andrew Dunstan <and...@dunslane.net> writes: > On 4/2/22 06:57, Andrew Dunstan wrote: >> Here's a version that actually works. It produces traces that look like >> this: >> andrew@emma:pg_upgrade $ grep '([0-9]*s)' >> tmp_check/log/regress_log_002_pg_upgrade >> [21:55:06](63s) ok 1 - dump before running pg_upgrade >> [21:55:22](79s) ok 2 - run of pg_upgrade for new instance >> [21:55:27](84s) ok 3 - old and new dumps match after pg_upgrade >> [21:55:27](84s) 1..3
> I know there's a lot going on, but are people interested in this? It's a > pretty small patch to produce something that seems quite useful. I too think that the elapsed time is useful. I'm less convinced that the time-of-day marker is useful. It also seems kind of odd that the elapsed time accumulates rather than being reset for each line. As it stands one would be doing a lot of mental subtractions rather than being able to see directly how long each step takes. I suppose that on fast machines where each step is under one second, accumulation would be more useful than printing a lot of zeroes --- but on the other hand, those aren't the cases where you're going to be terribly concerned about the runtime. regards, tom lane