Fix minor thread handle leak in pg_test_fsync on Windows START_TIMER launches a new thread, but never closed the handle to it. We don't need the handle after starting the thread, so just close it right away. The program creates a timer for each benchmark phase, so this isn't a big leak at the moment, but it could become more serious if someone added START_TIMER to a loop. I didn't bother backpatching though.
Author: Harrison Booth <[email protected]> Discussion: https://www.postgresql.org/message-id/CAAH-eSVFy2GySdYEAtd9Wp=swka0tzzgkw2vro8gtaq3ndc...@mail.gmail.com Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/aa7b9cf132b013a4061e61c4393164f31d4f6930 Modified Files -------------- src/bin/pg_test_fsync/pg_test_fsync.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
