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: Christoph Berg <myon@debian.org>, David Steele <david@pgmasters.net>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, Daniel Gustafsson <daniel@yesql.se>, pgsql-hackers@lists.postgresql.org
Date: 2019-03-25T09:06:32Z
Lists: pgsql-hackers 
On 2019-03-21 12:51, Christoph Berg wrote:
> Re: David Steele 2019-03-20 <8a85bece-b18f-0433-acf3-d106b31f0271@pgmasters.net>
>>>> Oh, right. So the way to go would be to use _("FAILED       "), and
>>>> ask translators to use the same length.
>>>
>>> Note there's no translation for pg_regress.  All these _() markers are
>>> currently dead code.  It seems hard to become motivated to translate
>>> that kind of program.  I don't think it has much value, myself.
>>
>> This patch has been "Waiting on Author" since March 8th.  Do you know when
>> you'll have a new version ready?
> 
> Here is a new revision that blank-pads "ok" to the length of "FAILED".

committed

-- 
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.