[Commits] 9af13f0e9: Temporary: range locking should still assume foward ordering

Sergei Petrunia psergey at askmonty.org
Mon Apr 29 13:13:38 EEST 2019


revision-id: 9af13f0e966171ef8688484b2da7fa576a1b4574 (v5.8-1037-g9af13f0e9)
parent(s): 248acd10346428b078aed780183ffe7f9f3c6896
author: Sergei Petrunia
committer: Sergei Petrunia
timestamp: 2019-04-29 13:13:38 +0300
message:

Temporary: range locking should still assume foward ordering

---
 utilities/transactions/transaction_lock_mgr.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/utilities/transactions/transaction_lock_mgr.cc b/utilities/transactions/transaction_lock_mgr.cc
index 9b6fd9381..c98803acb 100644
--- a/utilities/transactions/transaction_lock_mgr.cc
+++ b/utilities/transactions/transaction_lock_mgr.cc
@@ -1204,7 +1204,7 @@ void RangeLockMgr::AddColumnFamily(const ColumnFamilyHandle *cfh) {
     if (!strcmp(cfh->GetComparator()->Name(), "RocksDB_SE_v3.10"))
       ltree_cmp = &fw_cmp_;
     else if (!strcmp(cfh->GetComparator()->Name(),"rev:RocksDB_SE_v3.10"))
-      ltree_cmp = &bw_cmp_;
+      ltree_cmp = &fw_cmp_; // temporary: use the same ordering
     else {
       assert(false);
       ltree_cmp= nullptr;


More information about the commits mailing list