delta/postgresql.git/doc/src/sgml/pgbench.sgml, branch master git.postgresql.org: git/postgresql.git Move pgbench from contrib/ to src/bin/ 2015-04-13T17:07:16+00:00 Peter Eisentraut peter_e@gmx.net 2015-03-11T02:33:24+00:00 81134af3ec09d67043833f8d614fd688f17cb213 Reviewed-by: Michael Paquier <michael.paquier@gmail.com> 
Reviewed-by: Michael Paquier <michael.paquier@gmail.com>
Fix busted markup. 2015-03-03T04:28:31+00:00 Tom Lane tgl@sss.pgh.pa.us 2015-03-03T04:28:31+00:00 d1479011744d80d80c669b5bd64dc32187f26c1e Evidently from commit 878fdcb843e087cc1cdeadc987d6ef55202ddd04. Per buildfarm. 
Evidently from commit 878fdcb843e087cc1cdeadc987d6ef55202ddd04.
Per buildfarm.
pgbench: Add a real expression syntax to \set 2015-03-02T19:21:41+00:00 Robert Haas rhaas@postgresql.org 2015-03-02T19:21:41+00:00 878fdcb843e087cc1cdeadc987d6ef55202ddd04 Previously, you could do \set variable operand1 operator operand2, but nothing more complicated. Now, you can \set variable expression, which makes it much simpler to do multi-step calculations here. This also adds support for the modulo operator (%), with the same semantics as in C. Robert Haas and Fabien Coelho, reviewed by Álvaro Herrera and Stephen Frost 
Previously, you could do \set variable operand1 operator operand2, but
nothing more complicated.  Now, you can \set variable expression, which
makes it much simpler to do multi-step calculations here.  This also
adds support for the modulo operator (%), with the same semantics as in
C.

Robert Haas and Fabien Coelho, reviewed by Álvaro Herrera and
Stephen Frost
Add --latency-limit option to pgbench. 2014-10-13T17:50:24+00:00 Heikki Linnakangas heikki.linnakangas@iki.fi 2014-10-13T17:25:56+00:00 98aed6c721763f2472ccd23b834baed9f83a944b This allows transactions that take longer than specified limit to be counted separately. With --rate, transactions that are already late by the time we get to execute them are skipped altogether. Using --latency-limit with --rate allows you to "catch up" more quickly, if there's a hickup in the server causing a lot of transactions to stall momentarily. Fabien COELHO, reviewed by Rukh Meski and heavily refactored by me. 
This allows transactions that take longer than specified limit to be counted
separately. With --rate, transactions that are already late by the time we
get to execute them are skipped altogether. Using --latency-limit with
--rate allows you to "catch up" more quickly, if there's a hickup in the
server causing a lot of transactions to stall momentarily.

Fabien COELHO, reviewed by Rukh Meski and heavily refactored by me.
Change the way latency is calculated with pgbench --rate option. 2014-09-11T09:57:32+00:00 Heikki Linnakangas heikki.linnakangas@iki.fi 2014-09-11T09:40:01+00:00 02e3bcc661598275a75a8649b48602dca7aeec79 The reported latency values now include the "schedule lag" time, that is, the time between the transaction's scheduled start time and the time it actually started. This relates better to a model where requests arrive at a certain rate, and we are interested in the response time to the end user or application, rather than the response time of the database itself. Also, when --rate is used, include the schedule lag time in the log output. The --rate option is new in 9.4, so backpatch to 9.4. It seems better to make this change in 9.4, while we're still in the beta period, than ship a 9.4 version that calculates the values differently than 9.5. 
The reported latency values now include the "schedule lag" time, that is,
the time between the transaction's scheduled start time and the time it
actually started. This relates better to a model where requests arrive at a
certain rate, and we are interested in the response time to the end user or
application, rather than the response time of the database itself.

Also, when --rate is used, include the schedule lag time in the log output.

The --rate option is new in 9.4, so backpatch to 9.4. It seems better to
make this change in 9.4, while we're still in the beta period, than ship a
9.4 version that calculates the values differently than 9.5.
doc: Various typo/grammar fixes 2014-08-30T15:52:36+00:00 Kevin Grittner kgrittn@postgresql.org 2014-08-30T15:52:36+00:00 05258761bf12a64befc9caec1947b254cdeb74c5 Errors detected using Topy (https://github.com/intgr/topy), all changes verified by hand and some manual tweaks added. Marti Raudsepp Individual changes backpatched, where applicable, as far as 9.0. 
Errors detected using Topy (https://github.com/intgr/topy), all
changes verified by hand and some manual tweaks added.

Marti Raudsepp

Individual changes backpatched, where applicable, as far as 9.0.
docs: Add missing period. 2014-08-14T19:19:43+00:00 Robert Haas rhaas@postgresql.org 2014-08-14T19:19:43+00:00 751b7041050b7b19bf3001633740616089973ab3 Fabien COELHO and Robert Haas 
Fabien COELHO and Robert Haas
Fix typo in \setrandom document. 2014-08-12T09:01:01+00:00 Fujii Masao fujii@postgresql.org 2014-08-12T09:01:01+00:00 d6ded369a7793c926661f492c153a6dd05afc5bc Fabien COELHO 
Fabien COELHO
pgbench: Allow \setrandom to generate Gaussian/exponential distributions. 2014-07-30T17:22:08+00:00 Robert Haas rhaas@postgresql.org 2014-07-30T17:22:08+00:00 ed802e7dc36059efbc6669b4bfeebad43f0898c1 Mitsumasa KONDO and Fabien COELHO, with further wordsmithing by me. 
Mitsumasa KONDO and Fabien COELHO, with further wordsmithing by me.
doc: Put new options in right order on reference pages 2014-07-15T19:08:16+00:00 Peter Eisentraut peter_e@gmx.net 2014-07-15T18:34:33+00:00 9a218c02b8f10bc5aa3a9227b0a30ad0b6bdf6a6