Details
- 
    Bug 
- 
    Status: Closed (View Workflow)
- 
    Major 
- 
    Resolution: Fixed
- 
    10.6, 10.4(EOL), 10.5(EOL), 10.7(EOL), 10.8(EOL), 10.9(EOL)
- 
    None
Description
While working on MDEV-27366 a potentially problematic piece of code was found in /storage/innobase/handler/ha_innodb.cc:
|              if ((active_index != MAX_KEY | 
| 	            && active_index == pushed_idx_cond_keyno) | 
| 	            || (pushed_rowid_filter && rowid_filter_is_active)) { | 
| 		       /* Push down an index condition or an end_range check. */ | 
|         ... | 
| 		if (active_index == pushed_idx_cond_keyno) { | 
| 			m_prebuilt->idx_cond = this; | 
| 		} | 
| 	}
 | 
The last condition satisfies when
| active_index == pushed_idx_cond_keyno == MAX_KEY | 
which doesn't look correct. After fixing MDEV-27366 there is no test case to reproduce this scenario.
Attachments
Issue Links
- relates to
- 
                    MDEV-27366 SIGSEGV in handler_index_cond_check on SELECT in connection with rowid_filter setting -         
- In Review
 
-