| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pgbench--new transaction type |
| Date: | 2012-06-20 17:42:32 |
| Message-ID: | CA+TgmoYE9Mo9N4_DopDDTP-L2kF+K=5Lxz1KVo_C=Z-0PsAg0A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 20, 2012 at 3:48 AM, Simon Riggs <simon(at)2ndquadrant(dot)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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2012-06-20 17:43:17 | Re: WAL format changes |
| Previous Message | Josh Berkus | 2012-06-20 17:40:06 | Re: Nasty, propagating POLA violation in COPY CSV HEADER |