| From: | Cédric Villemain <cedric(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Prakash Itnal <prakash074(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, rasna(dot)t(at)nokia(dot)com, sandhya(dot)k_s(at)nokia(dot)com |
| Subject: | Re: Auto-vacuum is not running in 9.1.12 |
| Date: | 2015-06-18 10:05:32 |
| Message-ID: | 558297EC.7000809@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 ?
--
Cédric Villemain +33 (0)6 20 30 22 52
http://2ndQuadrant.fr/
PostgreSQL: Support 24x7 - Développement, Expertise et Formation
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-06-18 12:13:56 | Re: Auto-vacuum is not running in 9.1.12 |
| Previous Message | Michael Paquier | 2015-06-18 06:52:29 | Re: The real reason why TAP testing isn't ready for prime time |