Re: pgbench -i progress output on terminal

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Amit Langote <amitlangote09(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgbench -i progress output on terminal
Date: 2019-12-02 13:30:14
Message-ID: alpine.DEB.2.21.1912021428160.11211@pseudo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-12-02 14:41:43 Re: Bogus EXPLAIN results with column aliases for mismatched partitions
Previous Message Daniel Gustafsson 2019-12-02 13:09:51 Re: Update minimum SSL version