-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
opt: panic in optbuilder #32270
Labels
A-sql-optimizer
SQL logical planning and optimizations.
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
Comments
jordanlewis
added
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
A-sql-optimizer
SQL logical planning and optimizations.
labels
Nov 13, 2018
cc @BramGruneir |
@jordanlewis, can I get the schema and complete query that failed? This is only a fragment of the query, with no schema, so it can't easily be repro'd. |
Sorry about that.
|
BramGruneir
added a commit
to BramGruneir/cockroach
that referenced
this issue
Nov 15, 2018
This add a new nightly roachtest that run SQLsmith against the latest master looking for panics. If this crashes, the cause of the crash can be found in the logs for the first (and only) node. This test is being checked in as a skip due to cockroachdb#32270. Release note: None
Just a head's up, the this is currently blocking the SQLsmith roachtest. Once it's fixed, please don't forget to re-enable that test. |
andy-kimball
added a commit
to andy-kimball/cockroach
that referenced
this issue
Nov 28, 2018
Fixes cockroachdb#32270. The panic occurs when hoisting an expression that has both a correlated and an uncorrelated subquery. The current code panics when calling Reconstruct on the relational input to the uncorrelated subquery. The fix is to test for relational inputs and skip over them. They are not correlated, and so no hoisting needs to be done within their subtree. Release note (sql change): Fix panic when expression contains both a correlated and uncorrelated subquery.
craig bot
pushed a commit
that referenced
this issue
Nov 29, 2018
32443: opt: Fix panic when hoisting expr with correlated subquery r=andy-kimball a=andy-kimball Fixes #32270. The panic occurs when hoisting an expression that has both a correlated and an uncorrelated subquery. The current code panics when calling Reconstruct on the relational input to the uncorrelated subquery. The fix is to test for relational inputs and skip over them. They are not correlated, and so no hoisting needs to be done within their subtree. Release note (sql change): Fix panic when expression contains both a correlated and uncorrelated subquery. Co-authored-by: Andrew Kimball <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-sql-optimizer
SQL logical planning and optimizations.
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
The text was updated successfully, but these errors were encountered: