Repeatable Read UPDATE WHERE clause sees latest committed (vs isolated) version


Version: 5.6.36-82.0 (Percona Server (GPL), Release 82.0, Revision 58e846a)

It seems like in a REPEATABLE_READ session,

  • the SELECT WHERE clause only sees the isolated version of a record (as expected)

  • but the UPDATE WHERE clause sees the latest committed version (by another session, vs the isolated version) of a record

test example is as described in,678692,678692#msg-678692

and seemed like could potentially be related to

just want to see if this behaviour is considered bug from a REPEATABLE_READ isolation perspective? or not really?