diff options
author | Andres Freund <andres@anarazel.de> | 2015-01-04 15:44:49 +0100 |
---|---|---|
committer | Andres Freund <andres@anarazel.de> | 2015-01-04 15:53:08 +0100 |
commit | a68b8aec71c8ab0aefe9888041172d1482c7d276 (patch) | |
tree | 27c3c40f9e0a6423c4cc67efc47db77d0cf121b9 | |
parent | f0e2770956a8a6975dd70dd0bc3fdec073b50493 (diff) |
Correctly handle test durations of more than 2147s in pg_test_timing.
Previously the computation of the total test duration, measured in
microseconds, accidentally overflowed due to accidentally using signed
32bit arithmetic. As the only consequence is that pg_test_timing
invocations with such, overly large, durations never finished the
practical consequences of this bug are minor.
Pointed out by Coverity.
Backpatch to 9.2 where pg_test_timing was added.
-rw-r--r-- | contrib/pg_test_timing/pg_test_timing.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contrib/pg_test_timing/pg_test_timing.c b/contrib/pg_test_timing/pg_test_timing.c index 0bf9127e105..903584677a5 100644 --- a/contrib/pg_test_timing/pg_test_timing.c +++ b/contrib/pg_test_timing/pg_test_timing.c @@ -116,7 +116,7 @@ test_timing(int32 duration) end_time, temp; - total_time = duration > 0 ? duration * 1000000 : 0; + total_time = duration > 0 ? duration * INT64CONST(1000000) : 0; INSTR_TIME_SET_CURRENT(start_time); cur = INSTR_TIME_GET_MICROSEC(start_time); |