Re: New features for pgbench
| От | NikhilS |
|---|---|
| Тема | Re: New features for pgbench |
| Дата | |
| Msg-id | d3c4af540702112247o771a2b6fud17ce8d9399b529f@mail.gmail.com обсуждение исходный текст |
| Ответ на | New features for pgbench (Greg Smith <gsmith@gregsmith.com>) |
| Ответы |
Re: New features for pgbench
|
| Список | pgsql-patches |
Hi,
--
EnterpriseDB http://www.enterprisedb.com
On 2/12/07, Greg Smith <gsmith@gregsmith.com> wrote:
From your patch I see that it augments the -l flag. IMHO it does not make sense to add another flag. We can save the "if" check and log the extended contents as part of -l itself.
I am sorry, but I do not understand the above. If I read it correctly, are you suggesting that the same database with a prior pgbench run be used for further pgbench runs? How is it useful? How can one guarantee consistency of observed tps values with this in place?
Regards,
Nikhils
The attached adds two new command line switches to pgbench:
-x: Generate extended detail in the latency log, including a timestamp
for each transaction
From your patch I see that it augments the -l flag. IMHO it does not make sense to add another flag. We can save the "if" check and log the extended contents as part of -l itself.
-X: Do extra cleanup after the run (vacuum on all tables, checkpoint)
before stopping the clock. This gives substantially more consistancy in
results between runs.
I am sorry, but I do not understand the above. If I read it correctly, are you suggesting that the same database with a prior pgbench run be used for further pgbench runs? How is it useful? How can one guarantee consistency of observed tps values with this in place?
Regards,
Nikhils
--
EnterpriseDB http://www.enterprisedb.com
В списке pgsql-patches по дате отправления: