Re: pgbench --progress-timestamp no longer works correctly

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgbench --progress-timestamp no longer works correctly
Date: 2017-04-11 11:36:26
Message-ID: 16409.1491910586@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Noah Misch <noah(at)leadboat(dot)com> writes:
> On Fri, Apr 07, 2017 at 09:58:07AM -0700, Jeff Janes wrote:
>> --progress-timestamp is supposed to make -P report a Unix Epoch time stamp,
>> for easy correlation with the entries in other log files (like the postgres
>> server log file using %n).
>>
>> But that broke in this commit:
>>
>> commit 1d63f7d2d180c8708bc12710254eb7b45823440f
>> Author: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
>> Date: Mon Jan 2 13:41:51 2017 -0500

> The above-described topic is currently a PostgreSQL 10 open item. Tom,
> since you committed the patch believed to have created it, you own this open
> item. If some other commit is more relevant or if this does not belong as a
> v10 open item, please let us know. Otherwise, please observe the policy on
> open item ownership[1] and send a status update within three calendar days of
> this message. Include a date for your subsequent status update. Testers may
> discover new open items at any time, and I want to plan to get them all fixed
> well in advance of shipping v10. Consequently, I will appreciate your efforts
> toward speedy resolution. Thanks.

I'll take a look, and either fix it or post another update before the
end of the week.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-04-11 11:47:34 Re: Host variables corresponding bytea type in ecpg
Previous Message Álvaro Hernández Tortosa 2017-04-11 11:32:58 Re: Letting the client choose the protocol to use during a SASL exchange