Re: pgbench -i progress output on terminal - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: pgbench -i progress output on terminal
Date
Msg-id alpine.DEB.2.21.1912021428160.11211@pseudo
Whole thread Raw
In response to Re: pgbench -i progress output on terminal  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
> Another question I have is why doing only that for the data 
> initialization phase?  Wouldn't it make sense to be consistent with the 
> other tools having --progress and do the same dance in pgbench's 
> printProgressReport()?

I thought of it but did not suggest it.

When running a bench I like seeing the last few seconds status to see the 
dynamic evolution at a glance, and overwriting the previous line would 
hide that.

-- 
Fabien.



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Update minimum SSL version
Next
From: Tom Lane
Date:
Subject: Re: Bogus EXPLAIN results with column aliases for mismatched partitions