Re: Reporting script runtimes in pg_regress

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Christoph Berg <myon(at)debian(dot)org>, David Steele <david(at)pgmasters(dot)net>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Reporting script runtimes in pg_regress
Date: 2019-03-25 09:06:32
Message-ID: 760d6933-60eb-bcde-7a42-95045fcd7b6a@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-03-21 12:51, Christoph Berg wrote:
> Re: David Steele 2019-03-20 <8a85bece-b18f-0433-acf3-d106b31f0271(at)pgmasters(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2019-03-25 09:29:46 Re: reorder pg_rewind control file sync
Previous Message Konstantin Knizhnik 2019-03-25 09:04:05 Re: libpq compression