|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>|
|Cc:||Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-hackers(at)lists(dot)postgresql(dot)org|
|Subject:||Re: Reporting script runtimes in pg_regress|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> Now that I see this in action, it makes the actual test results harder
> to identify flying by. I understand the desire to collect this timing
> data, but that is a special use case and not relevant to the normal use
> of the test suite, which is to see whether the test passes. Can we make
> this optional please?
Well, I want the buildfarm to produce this info, so it's hard to see
how to get that without the timings being included by default. I take
your point that it makes the display look a bit cluttered, though.
Would it help to put more whitespace between the status and the timing?
regards, tom lane
|Next Message||Dmitry Vasiliev||2019-02-11 14:39:49||Logical replication and restore from pg_basebackup|
|Previous Message||Evgeniy Efimkin||2019-02-11 13:30:22||Re: [WIP] CREATE SUBSCRIPTION with FOR TABLES clause (table filter)|