From: | Hannu Krosing <hannu(at)krosing(dot)net> |
---|---|
To: | Mike Mascari <mascarm(at)mascari(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: LRU and full table scans |
Date: | 2002-02-27 05:43:11 |
Message-ID: | 1014788591.2145.73.camel@rh72.home.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2002-02-27 at 13:09, Mike Mascari wrote:
> On general a discussion has been taking place regarding cached query
> plans and how MySQL invented them.
IMHO the discussion was about cached queries not query plans.
> Of course, this is totally false. I
> remembered a nice paragraph in the Oracle docs as to the process by
> which Oracle uses shared SQL areas to share the execution plan of
> identical statements, flushing the area whenever a dependent object was
> modified. In searching for the reference, however, I stumbled an
> interesting fact. Unlike normal queries where blocks are added to the
> MRU end of an LRU list, full table scans add the blocks to the LRU end
> of the LRU list.
This seems really elegant solution , much better than not caching at all
and much better than flushing the whole cache by a large table scan
> I was wondering, in the light of the discussion of
> using LRU-K, if PostgreSQL does, or if anyone has tried, this technique?
------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2002-02-27 05:53:35 | Re: single task postgresql |
Previous Message | Tom Lane | 2002-02-27 05:39:16 | Re: eWeek Poll: Which database is most critical to your |