On Mon, Jul 22, 2013 at 01:49:39PM -0400, Greg Smith wrote: > Very minor update with V19 here, to reflect Alvaro's comments. The > tricky part now reads like this: > > High rate limit schedule lag values,
"High values of the rate limit schedule lag measurement?" > 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. Cheers, David. -- David Fetter <da...@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fet...@gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
