Re: too much pgbench init output

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tomas Vondra <tv(at)fuzzy(dot)cz>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: too much pgbench init output
Date: 2012-10-23 16:02:13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Tomas Vondra wrote:

> I've been thinking about this a bit more, and do propose to use an
> option that determines "logging step" i.e. number of items (either
> directly or as a percentage) between log lines.
> The attached patch defines a new option "--logging-step" that accepts
> either integers or percents. For example if you want to print a line
> each 1000 lines, you can to this
> $ pgbench -i -s 1000 --logging-step 1000 testdb

I find it hard to get excited about having to specify a command line
argument to tweak this. Would it work to have it emit messages
depending on elapsed time and log scale of tuples emitted? So for
example emit the first message after 5 seconds or 100k tuples, then back
off until (say) 15 seconds have lapsed and 1M tuples, etc? The idea is
to make it verbose enough to keep a human satisfied with what he sees,
but not flood the terminal with pointless updates. (I think printing
the ETA might be nice as well, not sure).

Álvaro Herrera
PostgreSQL Development, 24x7 Support, Training & Services

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2012-10-23 16:12:53 Re: New statistics for WAL buffer dirty writes
Previous Message Alvaro Herrera 2012-10-23 15:35:23 Re: FDW for PostgreSQL