Re: pgbench--new transaction type
Peter Geoghegan <peter@2ndquadrant.com>
From: Peter Geoghegan <peter@2ndquadrant.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Simon Riggs <simon@2ndquadrant.com>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, Jeff Janes <jeff.janes@gmail.com>, Greg Smith <greg@2ndquadrant.com>, pgsql-hackers@postgresql.org
Date: 2012-06-20T18:41:49Z
Lists: pgsql-hackers
On 20 June 2012 18:42, Robert Haas <robertmhaas@gmail.com> wrote: > On Wed, Jun 20, 2012 at 3:48 AM, Simon Riggs <simon@2ndquadrant.com> wrote: >> I'm sure Jeff submitted this because of the need for a standard test, >> rather than the wish to actually modify pgbench itself. >> >> Can I suggest that we include a list of standard scripts with pgbench >> for this purpose? These can then be copied alongside the binary when >> we do an install. > > I was thinking along similar lines myself. At the least, I think we > can't continue to add a short option for every new test type. > Instead, maybe we could have --test-type=WHATEVER, and perhaps that > then reads whatever.sql from some compiled-in directory. That would > allow us to sanely support a moderately large number of tests. +1. As long as pgbench is considered to be the standard benchmarking tool (and I think that it is a general problem that it is), we ought to make an effort to give people more options. -- Peter Geoghegan http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training and Services