Date: Tue, 29 Mar 2016 22:48:00 +0200 (CEST)
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
cc: PostgreSQL Developers <pgsql-hackers@postgresql.org>
Subject: Re: pgbench stats per script & other stuff
In-Reply-To: <20160329192230.GA907630@alvherre.pgsql>
Message-ID: <alpine.DEB.2.10.1603292236170.5677@sto>
References: <20160329192230.GA907630@alvherre.pgsql>
User-Agent: Alpine 2.10 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org


>> Indeed. The documentation is manually edited when submitting changes so as
>> to minimize diffs, but then it does not correspond anymore to any actual
>> output, so it is easy to do it wrong.
>
> Well, you fixed the "latency stddev" line to the sample output too, but
> in my trial run that line was not displayed, only the latency average.
> What are the command line args that supposedly produced this output?
> Maybe we should add it as a SGML comment, or even display it to the
> doc's reader.

Good point.

The test above shows the stats if there was -P , -L & --rate, because 
under these conditions the necessary data was collected, so they can be 
computed. Thus the output in the documentation assumes that one of these 
was used. I nearly always use "-P 1".

Note that the documentation is not really precise, "will look similar to", 
so there is no commitment.

If you feel like removing the stddev line from the doc because it is not 
there with usual options, fine with me.

-- 
Fabien.


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers