Re: too much pgbench init output
| От | Tom Lane |
|---|---|
| Тема | Re: too much pgbench init output |
| Дата | |
| Msg-id | 16292.1346805343@sss.pgh.pa.us обсуждение |
| Ответ на | Re: too much pgbench init output (Peter Eisentraut <peter_e@gmx.net>) |
| Ответы |
Re: too much pgbench init output
|
| Список | pgsql-hackers |
Peter Eisentraut <peter_e@gmx.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@gmx.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 done100 tuples done1000 tuples done10000 tuples done100000 tuples done...
regards, tom lane
В списке pgsql-hackers по дате отправления: