From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
cc: Daniel Gustafsson <daniel@yesql.se>, pgsql-hackers@lists.postgresql.org
Subject: Re: Reporting script runtimes in pg_regress
In-reply-to: <6f1657f9-c58c-ba28-0013-d36a6f6fd246@2ndquadrant.com>
References: <16646.1549770618@sss.pgh.pa.us>
 <E7790843-B885-492B-8537-CC9FB39D5F97@yesql.se>
 <11413.1549835730@sss.pgh.pa.us>
 <6f1657f9-c58c-ba28-0013-d36a6f6fd246@2ndquadrant.com>
Comments: In-reply-to Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
	message dated "Mon, 11 Feb 2019 09:44:24 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6417.1549895430.1@sss.pgh.pa.us>
Date: Mon, 11 Feb 2019 09:30:30 -0500
Message-ID: <6418.1549895430@sss.pgh.pa.us>
Precedence: bulk

Peter Eisentraut <peter.eisentraut@2ndquadrant.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