pgsql: Fix pgbench progress report behaviour when pgbench or a query ge - Mailing list pgsql-committers

From Heikki Linnakangas
Subject pgsql: Fix pgbench progress report behaviour when pgbench or a query ge
Date
Msg-id E1ZAw9S-00050S-4N@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix pgbench progress report behaviour when pgbench or a query gets stuck.

There were two issues here. First, if a query got stuck so that it took
e.g. 5 seconds, and progress interval was 1 second, no progress reports were
printed until the query returned. Fix so that we wake up specifically to
print the progress report. Secondly, if pgbench got stuck so that it would
nevertheless not print a progress report on time, and enough time passes
that it's already time to print the next progress report, just skip the one
that was missed. Before this patch, it would print the missed one with 0 TPS
immediately after the previous one.

Fabien Coelho. Backpatch to 9.4, where progress reports were added.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/9031ff91a110f29e8bd4b74ddf2b5ced3ecbeaf4

Modified Files
--------------
src/bin/pgbench/pgbench.c |   47 +++++++++++++++++++++++++++++++++++++++++++--
1 file changed, 45 insertions(+), 2 deletions(-)


pgsql-committers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: pgsql: Lift the limitation that # of clients must be a multiple of # of
Next
From: Heikki Linnakangas
Date:
Subject: pgsql: Fix pgbench progress report behaviour when pgbench or a query ge