Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Cache a table
Geomancer wrote:
> "Howard J. Rogers" <hjr_at_dizwell.com> wrote in message
> news:<3f9660e8$0$9554$afc38c87_at_news.optusnet.com.au>...
>
>> Disagree. The issue is not whether it would tend to want to stay in the >> buffer cache or not, but whether it is at risk of being dislodged by a >> rogue, huge, tablescan.
I'm not enitrely sure what you're getting at, but none of this makes much sense. They invented the recycle buffer precisely so that full table scans can find a home in the Buffer Cache which wouldn't 'dislodge' other buffers of more long-lasting use.
The idea that Oracle refuses to cache blocks read via FTS is just silly: how could Oracle "know no other task would use them"? We might just as well abolish the buffer cache entirely and have done with it, if that were really true.
There *are* direct reads which by-pass the buffer cache, but a full table scan against a regular table wouldn't be one of them.
If you could be more precise about your sources, or what you are suggesting, I'll happily discuss it, but generally FTSes go via the buffer cache.
Regards
HJR
-- -------------------------------------------- See my brand new website, soon to be full of new articles: www.dizwell.com. Nothing much there yet, but give it time!! --------------------------------------------Received on Thu Oct 23 2003 - 04:21:29 CDT