From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <peter(at)2ndquadrant(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Reduced power consumption in autovacuum launcher process |
Date: | 2011-07-18 19:06:40 |
Message-ID: | 4E248440.2070802@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 18.07.2011 18:32, Tom Lane wrote:
> Robert Haas<robertmhaas(at)gmail(dot)com> writes:
>> On Mon, Jul 18, 2011 at 10:35 AM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> A wakeup once every half hour would surely not be an issue from a power
>>> consumption standpoint. However, I'm not sure I understand here: aren't
>>> we trying to remove the timeouts completely?
>
>> Well, in the case of the AV launcher, the issue is that the main loop
>> is timed by definition, cf. autovacuum_naptime, and the WaitLatch()
>> interface is apparently designed so that we can't sleep longer than 35
>> minutes.
>
> Hmm. Well, it's not too late to rethink the WaitLatch API, if we think
> that that might be a significant limitation.
Right, we can easily change the timeout argument to be in milliseconds
instead of microseconds.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2011-07-18 19:08:05 | Re: patch for 9.2: enhanced errors |
Previous Message | Robert Haas | 2011-07-18 19:00:43 | Re: Initial Review: JSON contrib modul was: Re: Another swing at JSON |