Re: [HACKERS] Re: [COMMITTERS] pgsql: Remove pgbench "progress" test pending solution of its timing is (fwd)
Fabien COELHO <coelho@cri.ensmp.fr>
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
PostgreSQL Developers <pgsql-hackers@postgresql.org>
Date: 2018-07-18T13:01:34Z
Lists: pgsql-hackers
Attachments
- pgbench-tap-progress-6.patch (text/plain) patch
Hello Heikki, >> I did that in the attached version: no more environment variable hack, and >> no execution shortcut even if there is nothing to do. >> >> I also had to reproduce the progress logic to keep on printing report of >> (no) progress in this tailing phase. > > On second thoughts, there's one problem with this approach of always waiting > until -T is up. What if all the threads died because of errors? For example: Good corner-case catch! This behavior is indeed silly. > I don't think you want to wait in that situation. I think we should wait at > the end only if there some threads still alive, with nothing to do only > because of --rate. Yep. The attached version does only the tailing stuff under -R and not all threads were stopped on errors, with comments to tell about the why. I'm still wondering about a specific option to explicitely require this behavioral change. -- Fabien.
Commits
-
Refactor code to print pgbench progress reports.
- 9f75e3772350 12.0 landed
-
Fix pgbench TAP test to work in VPATH builds.
- e94f2bc809a0 11.0 cited