2010/5/11 Henning Westerholt henning.westerholt@1und1.de:
you could easily test if the number of records is too much for your current PKG_MEM pool setting by experiment. You should be able to observe memory allocation errors in the logs from the module or the database API. If you choose something like 1/2 or 2/3 of the maximum setting, you should be save.
Thanks. For now there are no entries in 'address' table (just 10-20 entries). Also PKG_MEM is 16 MB so I expect I will have enough time to add the fetch_count feature to the 'permissions' module :)
There is also another reason to prefer a partitioned loading mechanism, as it generate less fragmentation in the PKG_MEM pool, so its "easier" for the memory manager to cope with this workload.
Nice to know. Thanks a lot.