LRU and full table scans

Поиск
Список
Период
Сортировка
От Mike Mascari
Тема LRU and full table scans
Дата
Msg-id 3C7C9449.B747532B@mascari.com
обсуждение исходный текст
Ответы Re: LRU and full table scans  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: LRU and full table scans  (Hannu Krosing <hannu@krosing.net>)
Список pgsql-hackers
On general a discussion has been taking place regarding cached query
plans and how MySQL invented them. 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. I was wondering, in the light of the discussion of
using LRU-K, if PostgreSQL does, or if anyone has tried, this technique?

Mike Mascari
mascarm@mascari.


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tatsuo Ishii
Дата:
Сообщение: timestamp_part() bug?
Следующее
От: Dave Page
Дата:
Сообщение: Re: Rename sequence bug/feature