On Sep 25, 2009 at 12:26, inge inge@legos.fr wrote:
Hello,
Following our migration to SER 0.9.8, we have experienced the same problem (as describing below) when we wanted to restart SER.
I read about this problem that it should be necessary to modify the parameter PKG_MEM_POOL_SIZE for allocate more memory for each process.
What's the recommandation for memory allocation to be able to load location table in memory without have need to truncate the table ?
Try at least 4 Mb (but you could try much more, if it's too much and it won't be used it will have almost no impact on the "real" memory used). IIRC the problem appeared only at startup when the location data is preloaded in memory. The final destination is the shared memory, but there is a startup db query with temporarily stores the whole location in pkg_mem and this fails if more memory then PKG_MEM_POOL_SIZE is needed for it.
Andrei