diff options
| author | Andrew Dunstan <andrew@dunslane.net> | 2019-03-11 11:47:35 -0400 |
|---|---|---|
| committer | Andrew Dunstan <andrew@dunslane.net> | 2019-03-11 13:18:37 -0400 |
| commit | a47841528107921f02c280e0c5f91c5a1d86adb0 (patch) | |
| tree | a36e5d114e513d6ffab10259b4ba3905a068b88d /doc/src | |
| parent | a6e48da08844eeb5a72c8b59dad3aaab6e891fac (diff) | |
| download | postgresql-a47841528107921f02c280e0c5f91c5a1d86adb0.tar.gz postgresql-a47841528107921f02c280e0c5f91c5a1d86adb0.zip | |
pgbench: increase the maximum number of variables/arguments
pgbench's arbitrary limit of 10 arguments for SQL statements or
metacommands is far too low. Increase it to 256.
This results in a very modest increase in memory usage, not enough to
worry about.
The maximum includes the SQL statement or metacommand. This is reflected
in the comments and revised TAP tests.
Simon Riggs and Dagfinn Ilmari Mannsåker with some light editing by me.
Reviewed by: David Rowley and Fabien Coelho
Discussion: https://postgr.es/m/CANP8+jJiMJOAf-dLoHuR-8GENiK+eHTY=Omw38Qx7j2g0NDTXA@mail.gmail.com
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/ref/pgbench.sgml | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/src/sgml/ref/pgbench.sgml b/doc/src/sgml/ref/pgbench.sgml index 9d185248346..24833f46bcf 100644 --- a/doc/src/sgml/ref/pgbench.sgml +++ b/doc/src/sgml/ref/pgbench.sgml @@ -916,6 +916,8 @@ pgbench <optional> <replaceable>options</replaceable> </optional> <replaceable>d value can be inserted into a SQL command by writing <literal>:</literal><replaceable>variablename</replaceable>. When running more than one client session, each session has its own set of variables. + <application>pgbench</application> supports up to 255 variable uses in one + statement. </para> <table id="pgbench-automatic-variables"> |