Re: recreable/freeable chunks

Hi!

I wrote about recreatable chunk handling from memory and mixed up chunk freeing routines and chunk's data recreation routines: A callback routine is used when a process wants to free a recreatable chunk -> it can't reuse it just like that, because the original allocator (parent object) still has pointers pointing to this chunk, so the same object who allocated the chunk, has to do the freeing as well. That's my understanding, it'd be interesting to know whether it's correct ;)

Tanel.

> Recreatable:
> This chunk is used, but its contents can be regenerated if needed (such
are execution plans for cursors for example), thus Oracle can automatically reuse these chunks for others (of course when these chunks arenīt in use, thus unpinned). So when this information orignially stored in recreatable chunk is needed again, a callback function is executed, to recreate the contents in a chunk - callback functions containing instructions to recreate the information are registered for each recreatable chunk in heap manager's area if I recall correctly...)
> Information about unpinned recreatable chunks are held in heap LRU lists.

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Tanel Poder
  INET: tanel.poder.003_at_mail.ee

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).