Re: too much pgbench init output - Mailing list pgsql-hackers

From Robert Haas
Subject Re: too much pgbench init output
Date
Msg-id CA+TgmoZRHG5hE3X2fOWkcP82sLbfq7=-kzxmS3rrJiYvZwjZvQ@mail.gmail.com
Whole thread Raw
In response to too much pgbench init output  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: too much pgbench init output  ("Tomas Vondra" <tv@fuzzy.cz>)
Re: too much pgbench init output  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
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?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: 9.2rc1 build requirements
Next
From: Stefan Kaltenbrunner
Date:
Subject: Re: [COMMITTERS] pgsql: Cross-link to doc build requirements from install requirements.