> 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 -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers