• Annamalai Gurusami's avatar
    Bug #11765218 58157: INNODB LOCKS AN UNMATCHED ROW EVEN THOUGH USING · 357a008a
    Annamalai Gurusami authored
    RBR AND RC
    
    Description: When scanning and locking rows with < or <=, InnoDB locks
    the next row even though row based binary logging and read committed
    is used.
    
    Solution: In the handler, when the row is identified to fall outside
    of the range (as specified in the query predicates), then request the
    storage engine to unlock the row (if possible). This is done in
    handler::read_range_first() and handler::read_range_next().
    357a008a
handler.cc 143 KB