| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | greg(at)2ndQuadrant(dot)com |
| Cc: | coelho(at)cri(dot)ensmp(dot)fr, alvherre(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCH] pgbench --throttle (submission 7 - with lag measurement) |
| Date: | 2013-07-22 23:51:45 |
| Message-ID: | 20130723.085145.919230098455216324.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Very minor update with V19 here, to reflect Alvaro's comments. The
> tricky part now reads like this:
>
> High rate limit schedule lag values, that is lag values that are large
> compared to the actual transaction latency, indicate that something is
> amiss in the throttling process. High schedule lag can highlight a
> subtle problem there even if the target rate limit is met in the end.
I have committed this along with slight modification. I changed
"--rate rate" to "--rate=rate" to follow option style of pgbench.
Also I have removed a space in "--progress= sec" in the doc, which is
probably mistakenly added by previous commit.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-07-22 23:56:19 | Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |
| Previous Message | Andrew Dunstan | 2013-07-22 23:40:53 | Re: proposal - psql - show longest tables |