Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bNMSI-0004Jd-0q for pgsql-docs@arkaria.postgresql.org; Wed, 13 Jul 2016 15:52:10 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bNMSH-0001GZ-KM for pgsql-docs@arkaria.postgresql.org; Wed, 13 Jul 2016 15:52:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bNMRv-0000sJ-LO for pgsql-docs@postgresql.org; Wed, 13 Jul 2016 15:51:47 +0000 Received: from mail-lf0-x22b.google.com ([2a00:1450:4010:c07::22b]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bNMRs-0002mO-Ir for pgsql-docs@postgresql.org; Wed, 13 Jul 2016 15:51:47 +0000 Received: by mail-lf0-x22b.google.com with SMTP id q132so42559512lfe.3 for ; Wed, 13 Jul 2016 08:51:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:from:subject:message-id:date:user-agent:mime-version; bh=EuNYKTCnHb4rxQaSzs3GnnEDByuvfOORfWYUiDbDua8=; b=OcmtiA3U+I/jRMURjAcIRhjBPJf5rhfulBD6M054BYAsS2AEtBMo1GU9c7FQ1EGdLi mUuT99nD6+x9YTJfRqBMfTUWtb6PbwJJgsey1fpY/C0IlFpkPXttnFKRkV5uuyxSTS3z +R/95Af0+h/IDwVVk6vTNWJ+171tl63r14TBvJxwII+dJhW98jMsgv65j70810HKMCil Laub3H62AnmXlUtqFNMsqbtBXJax1cSx/nLdLjoFaBSHKfg74o9pojL3TizUE0bt4WKq 7Am7oFFLxPmIj5E3IHm2QDt5wf+f3cGQf31ekeMNPrwacVVhChoLuETKiFuwAvfY27Ax X3Yw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version; bh=EuNYKTCnHb4rxQaSzs3GnnEDByuvfOORfWYUiDbDua8=; b=Q5/MHcBKAxC88sZ3fTNF0ZVAtIw+9IlqY9ECb+U7ifIYJg9oLSdTg3VEurd52Wl9Af 8reM8ynLA7CTKOG+/eMEdCe9NkiDoOwszTigY8KBtfKQp952Pp1U28BHWKuvr15VL1PP rk6lgzgfCjw3hatDqnkcOtT3ivN4UpEiGPvd8kHYKyBGiQIirJdzOeL44/v+4JRcKHOQ N0+WQCHIjW5IID1Ie/G/QB3llhIL4N9DN4K/J7HbwYzU5QyIcaXXC+jBuu2Sysp9wvbG yNFs9ZQd8XJDbXwu6YTmv7DG2IVixTNSq26lFiQ08AVAUm0SaxD6vEIauLuyHe8JZboE +5oQ== X-Gm-Message-State: ALyK8tIb/lp7h8ohsIPg5huia5z8IS75lP+bFVppAqUNjGgSt9SVuoccYewX1Cpa21ibOg== X-Received: by 10.46.33.84 with SMTP id h81mr4588803ljh.47.1468425102719; Wed, 13 Jul 2016 08:51:42 -0700 (PDT) Received: from [1.0.0.7] ([109.196.196.155]) by smtp.gmail.com with ESMTPSA id e79sm63186lji.42.2016.07.13.08.51.41 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Jul 2016 08:51:42 -0700 (PDT) To: "pgsql-docs@postgresql.org" From: Alexander Law Subject: Incorrect 'last' adjective in pgbench.sgml Message-ID: <5786638C.8080508@gmail.com> Date: Wed, 13 Jul 2016 18:51:40 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------000105070000010000090503" X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org This is a multi-part message in MIME format. --------------000105070000010000090503 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello, Log format description in pgbench.sgml describes min_latency and max_latency as last two fields, but they are not last nowadays. Patch attached. Best regards, Alexander --------------000105070000010000090503 Content-Type: text/sgml; name="pgbench.sgml" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="pgbench.sgml" diff --git a/doc/src/sgml/ref/pgbench.sgml b/doc/src/sgml/ref/pgbench.sgml index f3afedb..323f2c7 100644 --- a/doc/src/sgml/ref/pgbench.sgml +++ b/doc/src/sgml/ref/pgbench.sgml @@ -1202,7 +1202,7 @@ END; within the interval, latency_sum is a sum of latencies (so you can compute average latency easily). The following two fields are useful for variance estimation - latency_sum is a sum of latencies and - latency_2_sum is a sum of 2nd powers of latencies. The last two + latency_2_sum is a sum of 2nd powers of latencies. The next two fields are min_latency - a minimum latency within the interval, and max_latency - maximum latency within the interval. A transaction is counted into the interval when it was committed. The fields in the end, --------------000105070000010000090503 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs --------------000105070000010000090503--