Range checks of pg_test_fsync --secs-per-test and pg_test_timing --duration
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-08-06T06:27:59Z
Lists: pgsql-hackers
Attachments
- pgtest-fix-range.patch (text/x-diff) patch
Hi all, As $subject says, pg_test_fsync and pg_test_timing don't really check the range of option values specified. It is possible for example to make pg_test_fsync run an infinite amount of time, and pg_test_timing does not handle overflows with --duration at all. These are far from being critical issues, but let's fix them at least on HEAD. So, please see the attached, where I have also added some basic TAP tests for both tools. Thanks, -- Michael
Commits
-
Improve range checks of options for pg_test_fsync and pg_test_timing
- 4d29e6dbd0bb 14.0 landed