| From: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com> |
|---|---|
| To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: pgbench -T isn't a hard cutoff. |
| Date: | 2011-08-29 03:34:54 |
| Message-ID: | CAJW2+qfNxgwaYbK9EZL2p6r_bXmp996jga=UWWCUmBT7yq4jdQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Aug 29, 2011 at 12:22, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> It's hard to justify making a change that will produce less accurate results
> in the vast majority of cases, just to improve behavior in a situation where
> useless results are coming out no matter what.
When I added -T option, I only expected standard pgbench transactions.
Since they are short enough, the difference should not be large.
If you have a plan to execute custom queries that take 1 second
or more, a hard cut-off makes senses.
--
Itagaki Takahiro
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexey Klyukin | 2011-08-29 11:20:56 | the '::' cast doesn't work in the FROM clause |
| Previous Message | Greg Smith | 2011-08-29 03:22:54 | Re: pgbench -T isn't a hard cutoff. |