Re: Reporting script runtimes in pg_regress - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Reporting script runtimes in pg_regress
Date
Msg-id 422e0383-79e1-7c10-5771-1e232e3349ca@2ndquadrant.com
Whole thread Raw
In response to Re: Reporting script runtimes in pg_regress  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Reporting script runtimes in pg_regress  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Reporting script runtimes in pg_regress  (John Naylor <john.naylor@2ndquadrant.com>)
List 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


pgsql-hackers by date:

Previous
From: Konstantin Knizhnik
Date:
Subject: Re: libpq compression
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Time to change pg_regress diffs to unified by default?