| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Jason Petersen *EXTERN*" <jason(at)citusdata(dot)com>, Atri Sharma <atri(dot)jiit(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Peter Geoghegan <pg(at)heroku(dot)com>, "Greg Stark" <stark(at)mit(dot)edu>, Ants Aasma <ants(at)cybertec(dot)at>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Clock sweep not caching enough B-Tree leaf pages? |
| Date: | 2014-04-22 07:29:08 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B17CF2458@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jason Petersen wrote:
> Yes, we obviously want a virtual clock. Focusing on the use of gettimeofday seems silly to me: it was
> something quick for the prototype.
>
> The problem with the clocksweeps is they don’t actually track the progression of “time” within the
> PostgreSQL system.
Would it make sense to just cache the result of the latest gettimeofday() call
and use that as an approximation for wall time?
The busier the system is, the more accurate that should be.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Atri Sharma | 2014-04-22 07:32:03 | Re: Clock sweep not caching enough B-Tree leaf pages? |
| Previous Message | Peter Geoghegan | 2014-04-22 06:57:04 | Re: Clock sweep not caching enough B-Tree leaf pages? |