Re: Re: Reporting script runtimes in pg_regress

From: Christoph Berg <myon(at)debian(dot)org>
To: David Steele <david(at)pgmasters(dot)net>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Peter Eisentraut <peter(dot)eisentraut(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: Re: Reporting script runtimes in pg_regress
Date: 2019-03-21 11:51:00
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

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


Attachment Content-Type Size
0001-Align-timestamps-in-pg_regress-output.patch text/x-diff 891 bytes

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Karlsson 2019-03-21 12:12:23 Re: PostgreSQL pollutes the file system
Previous Message Antonin Houska 2019-03-21 11:46:19 Re: "WIP: Data at rest encryption" patch and, PostgreSQL 11-beta3