Re: [HACKERS] pgbench --progress-timestamp no longer works correctly - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] pgbench --progress-timestamp no longer works correctly
Date
Msg-id 16409.1491910586@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] pgbench --progress-timestamp no longer works correctly  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
Noah Misch <noah@leadboat.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@sss.pgh.pa.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



pgsql-hackers by date:

Previous
From: Álvaro Hernández Tortosa
Date:
Subject: Re: [HACKERS] Letting the client choose the protocol to use during aSASL exchange
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Host variables corresponding bytea type in ecpg