Josh Berkus <j...@agliodbs.com> writes:
> Now ... can we decrease CPU overhead (wakeups) if we only check once per
> minute? If so, there's a good argument for making 1min the minimum.
Polling wakeups are right out, and are unnecessary anyway. The
utils/misc/timeout.c infrastructure calculates the time left till the
closest timeout event. So I don't see a need to worry about that end of
it.
ISTM our realistic options are for seconds or msec as the unit. If it's
msec, we'd be limited to INT_MAX msec or around 600 hours at the top end,
which seems like enough to me but maybe somebody thinks differently?
Seconds are probably OK but I'm worried about somebody complaining that
that's not enough resolution, especially as machines get faster.
Whichever the unit, I don't see a reason to set a lower bound different
from "one". You ask for a 1ms timeout, we'll give it to you, it's your
problem whether that's sane in your environment.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
