Bryan,

My problems came from a simple query containing an IN clause with 5000 items in it. I went over this easily by increasing the stack size limit to 1024 KB. The question I'm asking is if there are some best practicing in sizing the heap and stack for the Derby process based on the query complexities, number of database objects and estimated amount of data.

Regards,
Robert

Bryan Pendleton wrote:
I guess someone with more knowledge about Derby's internals may be able to tell you why your specific query requires a larger stack size.

I think that the query was noted to use an IN clause, so he
may be encountering either http://issues.apache.org/jira/browse/DERBY-47
or http://issues.apache.org/jira/browse/DERBY-713.

Robert, can you tell us more about the particular query that is giving
you trouble?

thanks,

bryan



Reply via email to