Horton

Re: Reporting script runtimes in pg_regress

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Daniel Gustafsson <daniel@yesql.se>, pgsql-hackers@lists.postgresql.org
Date: 2019-02-15T14:13:48Z
Lists: pgsql-hackers 
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

Commits

  1. Align timestamps in pg_regress output

  2. De-clutter display of script runtimes in pg_regress.

  3. Add per-test-script runtime display to pg_regress.