From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Daniel Gustafsson <daniel@yesql.se>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Reporting script runtimes in pg_regress
Date: Fri, 15 Feb 2019 15:13:48 +0100
Message-ID: <422e0383-79e1-7c10-5771-1e232e3349ca@2ndquadrant.com> (raw)
In-Reply-To: <e265e2ae-e92e-5ab9-dc68-60b6cb047b3d@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>
<6418.1549895430@sss.pgh.pa.us>
<e265e2ae-e92e-5ab9-dc68-60b6cb047b3d@2ndquadrant.com>
On 2019-02-15 14:32, Peter Eisentraut wrote:
> identity ... ok 238 ms
> partition_join ... ok 429 ms
> partition_prune ... ok 786 ms
> reloptions ... ok 94 ms
> hash_part ... ok 78 ms
> indexing ... ok 1298 ms
> partition_aggregate ... ok 727 ms
> partition_info ... ok 110 ms
> test event_trigger ... ok 128 ms
> test fast_default ... ok 173 ms
> test stats ... ok 637 ms
We should also strive to align "FAILED" properly. This is currently
quite unreadable:
int4 ... ok (128 ms)
int8 ... FAILED (153 ms)
oid ... ok (163 ms)
float4 ... ok (231 ms)
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, tgl@sss.pgh.pa.us, daniel@yesql.se, pgsql-hackers@lists.postgresql.org
Subject: Re: Reporting script runtimes in pg_regress
In-Reply-To: <422e0383-79e1-7c10-5771-1e232e3349ca@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox