You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Figure out if there is some way to reduce the stack size back to normal (2MB rather than 2.5MB) or if the increased stack size is indicative of something more serious,
Describe alternatives you've considered
I think something in sqlparser has grown the stack space slightly so now we are hitting stack overflows. Maybe if we can find what exactly is on the stack when it overflows we can refactor datafusion (e.g. break a single large function into multiple smaller ones) to work around the issue
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem or challenge?
While upgrading to a new version of SQL parser , @MohamedAbdeen21 in #11453 we found that this query:
Causes a stack overflow in debug builds. There is no overflow on release builds.
To reproduce remove the workaround added in #11453 (specifically remove the stack size override):
datafusion/datafusion/sqllogictest/bin/sqllogictests.rs
Line 37 in 382bf4f
And then run this command
cargo test --features=backtrace --test sqllogictests -- array.slt
I ran the program under lldb and here is the stack trace on my M3 mac
Describe the solution you'd like
Figure out if there is some way to reduce the stack size back to normal (2MB rather than 2.5MB) or if the increased stack size is indicative of something more serious,
Describe alternatives you've considered
I think something in sqlparser has grown the stack space slightly so now we are hitting stack overflows. Maybe if we can find what exactly is on the stack when it overflows we can refactor datafusion (e.g. break a single large function into multiple smaller ones) to work around the issue
Additional context
No response
The text was updated successfully, but these errors were encountered: