From: | "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, 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:28:02 |
Message-ID: | 20110718192802.GG19928@staff-mud-56-27.rice.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jul 18, 2011 at 03:12:20PM -0400, Tom Lane wrote:
> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> > On 18.07.2011 18:32, Tom Lane wrote:
> >> 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.
>
> On the whole I'd be more worried about giving up the shorter waits than
> the longer ones --- it's not too hard to imagine using submillisecond
> timeouts in the future, as machines get faster. If we really wanted to
> fix this, I think we need to move to a wider datatype.
>
> regards, tom lane
>
You could also tag the high bit to allow you to encode larger ranges
by having microseconds for the values with the high bit = 0 and use
milliseconds for the values with the high bit = 1. Then you could
have the best of both without punching up the width of the datatype.
Regard,
Ken
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2011-07-18 19:31:22 | Re: patch for 9.2: enhanced errors |
Previous Message | Tom Lane | 2011-07-18 19:26:44 | Re: per-column generic option |