You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to have a timestamp in a gstat report otherwise it is necessary to rely on the file creation date, which is not always correct.
This could be the first line of gstat output, just before the Database "/path/to/my.fdb" line.
Perhaps something like
Gstat execution time Sep 30, 2017 12:00:00
I would guess that this might be easy enough to add to 2.5.8, 30.3 and 4.0
It might also be useful to add a timestamp at the end of the output as large databases can take quite a while to analyse.
As temp. workaround for this one may use 3rd-party utility like mtee /t+ (on Windows) (or supertee -tn (on POSIX):
gstat -r ... 2>&1 | mtee /t+ .\gstat-with-timing.log
supertee -tn ./gstat-with-timing.log gstat -r ...
Submitted by: @reevespaul
It would be nice to have a timestamp in a gstat report otherwise it is necessary to rely on the file creation date, which is not always correct.
This could be the first line of gstat output, just before the Database "/path/to/my.fdb" line.
Perhaps something like
Gstat execution time Sep 30, 2017 12:00:00
I would guess that this might be easy enough to add to 2.5.8, 30.3 and 4.0
It might also be useful to add a timestamp at the end of the output as large databases can take quite a while to analyse.
Commits: 7a1f070 244e4be 1f811f8 4eac322
====== Test Details ======
See test for CORE0959
The text was updated successfully, but these errors were encountered: