Re: Autovacuum launcher doesn't notice death of postmaster immediately - Mailing list pgsql-hackers

From Zeugswetter Andreas ADI SD
Subject Re: Autovacuum launcher doesn't notice death of postmaster immediately
Date
Msg-id E1539E0ED7043848906A8FF995BDA579021B347A@m0143.s-mxs.net
Whole thread Raw
In response to Re: Autovacuum launcher doesn't notice death of postmaster immediately  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Autovacuum launcher doesn't notice death of postmaster immediately  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
> > > > > The launcher is set up to wake up in autovacuum_naptime
seconds
> > > > > at most.
> >
> > Imho the fix is usually to have a sleep loop.
>
> This is what we have.  The sleep time depends on the schedule
> of next vacuum for the closest database in time.  If naptime
> is high, the sleep time will be high (depending on number of
> databases needing attention).

No, I meant a "while (sleep 1(or 10) and counter < longtime) check for
exit" instead of "sleep longtime".

Andreas


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCHES] [BUGS] BUG #3326: Invalid lower bound of autovacuum_cost_limit
Next
From: Andrew Sullivan
Date:
Subject: Re: COPYable logs status