Re: [HACKERS] pgbench --progress-timestamp no longer works correctly

2017-04-11 Thread Tom Lane
Jeff Janes writes: > --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

Re: [HACKERS] pgbench --progress-timestamp no longer works correctly

2017-04-11 Thread Tom Lane
Noah Misch 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). >> >>

Re: [HACKERS] pgbench --progress-timestamp no longer works correctly

2017-04-10 Thread Noah Misch
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

[HACKERS] pgbench --progress-timestamp no longer works correctly

2017-04-07 Thread Jeff Janes
--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