pgsql: Refactor code to print pgbench progress reports.

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Refactor code to print pgbench progress reports.
Date: 2019-03-25 16:09:28
Message-ID: E1h8SAC-0001oV-Uw@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Refactor code to print pgbench progress reports.

threadRun() function is very long and deeply-nested. Extract the code to
print progress reports to a separate function, to make it slightly easier
to read.

Author: Fabien Coelho
Discussion: https://www.postgresql.org/message-id/alpine.DEB.2.21.1903101225270.17271%40lancre

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/9f75e3772350fb66f20a3d7f33bc94f30300d7eb

Modified Files
--------------
src/bin/pgbench/pgbench.c | 177 ++++++++++++++++++++++++----------------------
1 file changed, 94 insertions(+), 83 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2019-03-25 16:23:56 pgsql: Further code review for new integerset code.
Previous Message Robert Haas 2019-03-25 15:28:45 Re: pgsql: Allow ATTACH PARTITION with only ShareUpdateExclusiveLock.