On Thu, 2003-03-06 at 01:13, Tom Lane wrote:
> Rod Taylor <rbt@rbt.ca> writes:
> > [ optimizing for small frequent queries ]
>
> What if the client doesn't come back with another query for awhile?
Yup.. Thats why I said you basically lose 1 seconds worth of stats (or
rather can't count on when they arrive).
But, that doesn't matter for most cases as you cannot cause a lot of
trouble with 1 seconds worth of activity. That said, I'd make the
actual value a GUC.
However, having the numbers off by a little (the %age they're off by
decreases with increased activity) is still a lot more useful than not
having any numbers at all.
Anyway, the basic proposal would be to change the on / off flags for row
& block level into a 'stats delay'. A large number would be off, 0
would have the same properties as today. Default to be determined (but
1 second seems to be plenty).
--
Rod Taylor <rbt@rbt.ca>
PGP Key: http://www.rbt.ca/rbtpub.asc