Bug #121061 InnoDB wrong result for a full-column secondary index on an externally stored field during MVCC lookup
Submitted: 6 Aug 8:37 Modified: 13 Aug 2:36
Reporter: Xu Leo Email Updates:
Status: Open Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S2 (Serious)
Version:9.7, 8.4, 26.7, 8.0.46 OS:Any
Assigned to: CPU Architecture:Any
Tags: external field, innodb, MVCC, secondary index, wrong result

To submit contributions, please log in.