Re: [PATCH] add --progress option to pgbench (submission 3) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [PATCH] add --progress option to pgbench (submission 3)
Date
Msg-id CA+TgmoaJawAM0A4N1RnsndFhTOYYbwnt+7N7XWLcW=n-uDC79Q@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] add --progress option to pgbench (submission 3)  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: [PATCH] add --progress option to pgbench (submission 3)  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
On Wed, Jun 26, 2013 at 7:16 AM, Fabien COELHO <coelho@cri.ensmp.fr> wrote:
> Here is a v4 that takes into account most of your points: The report is
> performed for all threads by thread 0, however --progress is not supported
> under thread fork emulation if there are more than one thread. The report
> time does not slip anymore.

I don't believe that to be an acceptable restriction.  We generally
require features to work on all platforms we support.  We have made
occasional compromises there, but generally only when the restriction
is fundamental to the platform rather than for developer convenience.

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



pgsql-hackers by date:

Previous
From: Boszormenyi Zoltan
Date:
Subject: Re: Error code returned by lock_timeout
Next
From: Robert Haas
Date:
Subject: Re: Group Commits Vs WAL Writes