Re: Reporting script runtimes in pg_regress
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2019-02-10T21:55:30Z
Lists: pgsql-hackers
Daniel Gustafsson <daniel@yesql.se> writes: >> On 10 Feb 2019, at 04:50, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Does anyone else feel that this is interesting/useful data? > Absolutely, +1 on this. In Greenplum we print the runtime of the script and > the runtime of the diff, both of which have provided useful feedback on where > to best spend optimization efforts (the diff time of course being a lot less > interesting in upstream postgres due to gpdb having it’s own diff tool to > handle segment variability). Seems like I'm far from the first to think of this --- I wonder why nobody submitted a patch before? Anyway, pushed. regards, tom lane
Commits
-
Align timestamps in pg_regress output
- 148cf5f462e5 12.0 landed
-
De-clutter display of script runtimes in pg_regress.
- 93b5cc039e23 12.0 landed
-
Add per-test-script runtime display to pg_regress.
- 72d71e03563b 12.0 landed