Thanks for the improvement!
I have a small reservation about "finish/end time schedule" in the second
paragraph, or maybe there is something that I do not understand. There is
no schedule for finishing anything, only start times are scheduled, so I
wish the text could avoid suggesting that finish time are scheduled.
The rate is targeted by starting transactions along a
Poisson-distributed schedule time line. The expected
finish time schedule
-> start time schedule
moves forward based on when the client first started, not when
the previous transaction ended.
That approach means that when transactions go past their original
scheduled end time, it is possible for later ones to catch up again.
-> That approach means that long transactions can result in later
transactions to be late with respect to the schedule, while short
transactions makes it possible for late ones to catch up again.
Would you be ok with that?
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription: