Commits on Apr 29, 2024

1. Add range locking support for MyRocks …

   - Add new sysvar, rocksdb_use_range_locking. When it's on:
   - RocksDB is initialized to used range-locking lock manager
   - For all DML operations (including SELECT ... FOR UPDATE), the scanned range
     will be locked before reading/modifying rows
   - For all DML operations, MyRocks will read and modify the latest committed
     data, just like InnoDB does, because there is no snapshot checking if range
     locking is used.
   - Introduce a RocksDB locking iterator, which reads the rows, locks the range,
   - and re-reads the rows. It is used for queries that do not have a finite range
     to scan, like UPDATE t1 ... ORDER BY t1.key LIMIT n
   - Add another new sysvar, rocksdb_use_range_lock_manager_as_point, which uses
     the point locking algorithm but the lock manager used is the range one.
   - Add enabled rocksdb_use_range_locking as another MTR rocksdb suite test
     combination.
   
   Co-authored-by: Sergei Petrunia <[email protected]>
   Co-authored-by: Laurynas Biveinis <[email protected]>

   

   laurynas-biveinis and spetrunia committed Apr 29, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for 307be4d
   • Browse repository at this point

   Copy the full SHA

   307be4d View commit details

   Browse the repository at this point in the history

2. TODO: PR this separately

   

   laurynas-biveinis committed Apr 29, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for 5f7e036
   • Browse repository at this point

   Copy the full SHA

   5f7e036 View commit details

   Browse the repository at this point in the history

3. TODO fixes

   

   laurynas-biveinis committed Apr 29, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for 3b35dab
   • Browse repository at this point

   Copy the full SHA

   3b35dab View commit details

   Browse the repository at this point in the history