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
subselect losing the index when where clause includes coalesce() [CORE4640] #4954
Comments
Commented by: Omacht András (aomacht) database for the test case |
Modified by: Omacht András (aomacht)Attachment: FB_TEST.ZIP [ 12650 ] |
Commented by: Omacht András (aomacht) Dmitry, yes, it looks like it's the same problem. |
Commented by: @dyemanov I'll try, but no promises. |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Deferred Test Details: Deferred until core-2975 will be fixed (currently 2.5.x produces still bad plan: PLAN MERGE (SORT (JOIN (T1 INDEX (T1_COL), T2 INDEX (T2_ID))), SORT (T3 NATURAL)); 3.0 & 4.0: PLAN HASH (JOIN (T1 INDEX (T1_COL), T2 INDEX (T2_ID)), T3 NATURAL) ) |
Submitted by: Omacht András (aomacht)
Attachments:
FB_TEST.ZIP
See the attached database.
When running
no indicies were found for view V1:
The engine should use T1_UK and T2_UK:
Without
coalesce
in then where clause it works fine:and
====== Test Details ======
Deferred until core-2975 will be fixed (currently 2.5.x produces still bad plan: PLAN MERGE (SORT (JOIN (T1 INDEX (T1_COL), T2 INDEX (T2_ID))), SORT (T3 NATURAL)); 3.0 & 4.0: PLAN HASH (JOIN (T1 INDEX (T1_COL), T2 INDEX (T2_ID)), T3 NATURAL) )
The text was updated successfully, but these errors were encountered: