Viewing all changes in revision 2502.1195.2.
- Committer: Annamalai Gurusami
- Date: 2012-07-12 11:12:07 UTC
- mto: (2502.1198.2 mysql-5.1) (2643.137.22 5.1-merge-all)
- mto: This revision was merged to the branch mainline in revision 3182.
- Revision ID: annamalai.gurusami@oracle.com-20120712111207-wj9kvlysg1yeafny
Bug #11765218 58157: INNODB LOCKS AN UNMATCHED ROW EVEN THOUGH USING
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().
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().
- files modified:
- sql/handler.cc
expand all
collapse all
added
removed
