Re: SPL & Triggers - do's and don'ts

In article <329E8051.3FF@sprynet.com>, Jake Salomon <jsalomon@sprynet.com> writes >Mark D. Stock wrote: >> >> David Williams wrote: >> > >> > In article <3291472D.5831@sprynet.com>, Jake Salomon >> > <jsalomon@sprynet.com> writes >> > >As far as I recall, the SP cache is still limited to 50 procs. This is >> > >not [yet] a tunable to keep those feature requests coming, folks! >> > > >> > Where did you hear about this limit - I cannot find it in the >> > manuals. >> >> It's always been a tunable parameter, well in 7.xx anyway, just not >> documented. ;-) >> >> I'm not at the office at the moment, but if memory serves me, the parameter >> is something like PCPOOL_SIZE, and defaults to 50. So this is where the >> so-called limit comes from. As to the maximum value for this parameter... >> I haven't a clue. :-) >> >> Hope this helps, > >Mark, > >yes, it will help. This cache limit has always been my reason for not >embedding much of the app in SPL.. If this limit can truly be raised, I >will retract my primary objection (while maintaining my other objection >- the database engine is not designed as a language processor.) I will >need to do some research myself as well. but thanks for pointing this >out. > > -- Jake Salomon I tried setting PCPOOL_SIZE = 100 and checked using onstat -g mem but the size of the procpool memory pool do not change.....???? How can I tell if this change worked?? -- David Williams