During the development of our tool, using Xquery on MonetDB, we ran onto the following error:
ERROR = !fatal error: aborted too deep recursion
From previous posts (I guess) I can conclude that this relates to an Xquery that simply is too big (too many operators) to create a good plan for it. All systems have limits that either cause an emergency stop. In this case,
Harm van Beek(DT) wrote: the operating system has such a limit.
I tried several MonetDB releases (May2009-SP2, Aug2009-SP2, Nov2009-DB0) on Red Hat Enterprise Linux Server release 5.4 (Tikanga), all showing the same result.
Does anyone have any directions on how to solve this?
Yes. Programming cleverness comes into play. Especially if you use a tool to generate queries, then that tool should be a little more conservative in the kind of queries generated.
Can we reconfigure the compiler to fix this (or recompile it with options)? No. At some point the optimization space becomes just too big. People that can spare the time to find the optimal settings for a larger application space are more then welcome to try it out on the source code made available.
regards, Martin
Thanks in advance!
Harm van Beek Netherlands Forensic Institute
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users