Thank you, committed
Fabien COELHO wrote:
--progress-timestamp use Unix epoch timestamps in ms for progress
A quibble, but it isn't in ms, it is in seconds. The digits after the decimal
point give a precision to the ms level, but they don't change the base unit.
Yes. The issue is
--progress-timestamp use Unix epoch timestamps in ms for progress
A quibble, but it isn't in ms, it is in seconds. The digits after the
decimal point give a precision to the ms level, but they don't change
the base unit.
Yes. The issue is mostly to keep the description under 80
On Wed, Sep 9, 2015 at 1:35 AM, Fabien COELHO wrote:
>
> In the sgml, second should be plural in 'intead of the number of second
>> since the'. And 'intead' should be 'instead'.
>>
>
> Ok.
>
> --progress-timestamp use a Unix-like epoch timestamp for progress
>>
In the sgml, second should be plural in 'intead of the number of second
since the'. And 'intead' should be 'instead'.
Ok.
--progress-timestamp use a Unix-like epoch timestamp for progress
reporting
but that is getting pretty long.
Indeed. I've done:
--progress-timestamp use
Use milliseconds for consistency with the '%n' log_prefix patch currently
submitted by Tomas Vondra in the CF.
sh> ./pgbench -P 1 -N -T 100 -c 2
starting vacuum...end.
progress: 1.0 s, 546.0 tps, lat 3.619 ms stddev 4.426
progress: 2.0 s, 575.0 tps, lat 3.480 ms stddev 1.705
sh>
On Mon, Sep 7, 2015 at 11:25 PM, Fabien COELHO wrote:
>
> Use milliseconds for consistency with the '%n' log_prefix patch currently
>>> submitted by Tomas Vondra in the CF.
>>>
>>> sh> ./pgbench -P 1 -N -T 100 -c 2
>>> starting vacuum...end.
>>> progress: 1.0 s, 546.0
On Sun, Aug 23, 2015 at 4:25 AM, Fabien COELHO wrote:
>
> It is not easy to compare events on a pgbench runs (oops, the tps is down)
> with for instance events in postgres log, so as to figure out what may have
> cause a given glitch.
>
> This patches adds an option to
It is not easy to compare events on a pgbench runs (oops, the tps is down)
with for instance events in postgres log, so as to figure out what may
have cause a given glitch.
This patches adds an option to replace the time since pgbench run
started with a timestamp in the progress report so