On Tue, Dec 19, 2017 at 03:57:46PM +0000, Sharma, Sreejith wrote:
All,
I have a valid scenario where our application generates a SQL which is around 4.4MB and contains 75K of combination of AND and OR operators. This SQL fails with “SELECT: too many nested operators” error while executing this SQL.
While I went through the code, I noticed any thread size above THREAD_STACK_SIZE - 16 * 1024 is getting aborted. Is there any possibility that we can change this? Any reason why it’s set to 16MB? As server our server has enough memory and storage and we need to understand if this can be handled in code or via parameter as this is valid scenario. Also, we can’t split the SQL too.
I think most thread libraries have the default THREAD_STACK_SIZE at 2M. The 16K is a boundary we need, as not all functions are directly protected by this stack overflow protection mechanism.
niels
Regards,
Sreejith
users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list