Alvaro Herrera <alvhe...@2ndquadrant.com> writes:
> Yeah, the case is pretty weird and I'm not really sure that the server
> ought to be expected to behave. But if this is actually the only part
> of the server that misbehaves because of sudden gigantic time jumps, I
> think it's fair to patch it. Here's a proposed patch.
I think the parenthetical bit in the comment should read "plus any
fractional second, for simplicity". Also, maybe replace "300" by
a #define constant MAX_AUTOVAC_SLEEPTIME for readability?
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
