Cédric Villemain wrote:
> 
> 
> Le 17/06/2015 23:10, Alvaro Herrera a écrit :
> > Tom Lane wrote:
> >> launcher_determine_sleep() does have a minimum sleep time, and it seems
> >> like we could fairly cheaply guard against this kind of scenario by also
> >> enforcing a maximum sleep time (of say 5 or 10 minutes).  Not quite
> >> convinced whether it's worth the trouble though.
> > 
> > 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.
> 
> Does that still respect an autovacuum_naptime (GUC) greater than 5 minutes ?

Yes, sure.  The launcher will wake up, see time-to-vacuum further away,
then continue sleeping.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Reply via email to