revision-id: d4bf4b4197d8887c119bcb5d87db6ba5feb9aabc (v5.8-1026-gd4bf4b419) parent(s): 46d49ea0b7e0267b5c360d45d90a64776477b8ed author: Sergei Petrunia committer: Sergei Petrunia timestamp: 2019-04-05 20:19:18 +0300 message: Fix range_locking_test.cc Now use_range_locking is a part of TransactionDBOptions, not a member of TransactionDB. --- utilities/transactions/range_locking_test.cc | 1 - 1 file changed, 1 deletion(-) diff --git a/utilities/transactions/range_locking_test.cc b/utilities/transactions/range_locking_test.cc index 447e4c44e..26ee9b84c 100644 --- a/utilities/transactions/range_locking_test.cc +++ b/utilities/transactions/range_locking_test.cc @@ -72,7 +72,6 @@ class RangeLockingTest : public ::testing::Test { s = TransactionDB::Open(options, txn_db_options, dbname, &db); assert(s.ok()); - db->use_range_locking= true; rocksdb::RangeLockMgrControl *mgr= db->get_range_lock_manager(); assert(mgr); // can also: mgr->set_max_lock_memory(rocksdb_max_lock_memory);