From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: too much pgbench init output |
Date: | 2012-09-05 00:35:43 |
Message-ID: | 16292.1346805343@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On 9/1/12 6:30 AM, Robert Haas wrote:
>> On Sat, Sep 1, 2012 at 12:00 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>>> When initializing a large database, pgbench writes tons of "%d tuples
>>> done" lines. I propose to change this to a sort of progress counter
>>> that stays on the same line, as in the attached patch.
>> I'm not sure I like this - what if the output is being saved off to a file?
> I suppose we could print \n instead of \r then.
Possibly off-the-wall idea: we could fix the "too much output" problem
once and for all by going to a log scale.
10 tuples done
100 tuples done
1000 tuples done
10000 tuples done
100000 tuples done
...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-09-05 00:37:52 | Re: build farm machine using <make -j 8> mixed results |
Previous Message | Heikki Linnakangas | 2012-09-05 00:34:59 | Re: Cascading replication and recovery_target_timeline='latest' |