pgbench --progress-timestamp no longer works correctly
Jeff Janes <jeff.janes@gmail.com>
From: Jeff Janes <jeff.janes@gmail.com>
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2017-04-07T16:58:07Z
Lists: pgsql-hackers
--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
Use clock_gettime(), if available, in instr_time measurements.
The commit before that one changed pgbench to make it tolerate the change
in clock, but it overlooked --progress-timestamp.
Cheers,
Jeff
Commits
-
Fix pgbench's --progress-timestamp option to print Unix-epoch timestamps.
- feffa0e0795a 10.0 landed
-
Use clock_gettime(), if available, in instr_time measurements.
- 1d63f7d2d180 10.0 cited