diff --git a/doc/src/sgml/ref/pgbench.sgml b/doc/src/sgml/ref/pgbench.sgml index 541d17b82a030aec1f201d7cb3e28cab5bf47173..42d06671800d223a15e0f1ad7dc039919f9e80ba 100644 --- a/doc/src/sgml/ref/pgbench.sgml +++ b/doc/src/sgml/ref/pgbench.sgml @@ -48,7 +48,7 @@ Typical output from pgbench looks like: -transaction type: TPC-B (sort of) +transaction type: <builtin: TPC-B (sort of)> scaling factor: 10 query mode: simple number of clients: 10 @@ -261,6 +261,20 @@ pgbench options dbname benchmarking arguments: + + + + + + Add the specified builtin script to the list of executed scripts. + Available builtin scripts are: tpcb-like, + simple-update and select-only. + With special name list, show the list of builtin scripts + and exit immediately. + + + + clients @@ -307,14 +321,13 @@ pgbench options dbname - filename - filename + + - Read transaction script from filename. + Add a transaction script read from filename to + the list of executed scripts. See below for details. - , , and - are mutually exclusive. @@ -404,10 +417,8 @@ pgbench options dbname - Do not update pgbench_tellers and - pgbench_branches. - This will avoid update contention on these tables, but - it makes the test case even less like TPC-B. + Run builtin simple-update script. + Shorthand for @@ -512,9 +523,9 @@ pgbench options dbname Report the specified scale factor in pgbench's output. With the built-in tests, this is not necessary; the correct scale factor will be detected by counting the number of - rows in the pgbench_branches table. However, when testing - custom benchmarks (