postgresql

History

Tom Lane 67a875355e In pgbench logging, avoid assuming that instr_times match Unix timestamps. For aggregated logging, pg_bench supposed that printing the integer part of INSTR_TIME_GET_DOUBLE() would produce a Unix timestamp. That was already broken on Windows, and it's about to get broken on most other platforms as well. As in commit `74baa1e3b`, we can remove the entanglement at the price of one extra syscall per transaction; though here it seems more convenient to use time(NULL) instead of gettimeofday(), since we only need integral-second precision. I took the time to do some wordsmithing on the documentation about pgbench's logging features, too. Discussion: https://postgr.es/m/8837.1483216839@sss.pgh.pa.us	2017-01-02 12:26:03 -05:00
..
sgml	In pgbench logging, avoid assuming that instr_times match Unix timestamps.	2017-01-02 12:26:03 -05:00
Makefile	Remove maintainer-check target, fold into normal build	2013-10-10 20:11:56 -04:00

Tom Lane 67a875355e In pgbench logging, avoid assuming that instr_times match Unix timestamps.

For aggregated logging, pg_bench supposed that printing the integer part of
INSTR_TIME_GET_DOUBLE() would produce a Unix timestamp.  That was already
broken on Windows, and it's about to get broken on most other platforms as
well.  As in commit 74baa1e3b, we can remove the entanglement at the price
of one extra syscall per transaction; though here it seems more convenient
to use time(NULL) instead of gettimeofday(), since we only need
integral-second precision.

I took the time to do some wordsmithing on the documentation about
pgbench's logging features, too.

Discussion: https://postgr.es/m/8837.1483216839@sss.pgh.pa.us

2017-01-02 12:26:03 -05:00

sgml In pgbench logging, avoid assuming that instr_times match Unix timestamps. 2017-01-02 12:26:03 -05:00

Makefile Remove maintainer-check target, fold into normal build 2013-10-10 20:11:56 -04:00