RE: Why separate pools?

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

Thanks, Sue.  This jives better with my memory, suspect though it may be
<g>.  This is pretty close to my concept of "read-only" (program)
objects and "update-capable" (database) objects.

Joe

> From: Sue Baker
> 
> Hey, both of you are right, but for different parts of the
> equation.  Data can be accessed in any memory page regardless of
> the memory pool it is in.  Program specific logic and buffers
> cannot be accessed across memory pool boundaries, IIRC.
> 
> IE, if I've got 2 memory pools for my interactive work and user z
> loads up pgma in pool 1 and then user y loads up pgma in pool 2,
> there will be two copies of pgma in memory.  If user z reads
> record 12345 and then user y also reads 12345, user y will read
> from memory and not perform another fetch from disk.