From ac46790374e67d24862d70733bd3f4d1c2d26fae Mon Sep 17 00:00:00 2001 From: Sagar Vemuri Date: Mon, 17 Sep 2018 11:44:36 -0700 Subject: [PATCH] Fix sync-point comment in Block destructor (#4380) Summary: This is a follow up to #4370. The earlier comment is not correct. Thanks to ajkr for pointing this out. Pull Request resolved: https://github.com/facebook/rocksdb/pull/4380 Differential Revision: D9874667 Pulled By: sagar0 fbshipit-source-id: f4e092d86b29c715258210b770643d367e38caae --- table/block.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/table/block.cc b/table/block.cc index 2d662bb2d..c8247828e 100644 --- a/table/block.cc +++ b/table/block.cc @@ -763,8 +763,8 @@ BlockBasedTableOptions::DataBlockIndexType Block::IndexType() const { } Block::~Block() { - // This sync point can be re-enabled once the right order for global static - // initialization/destruction across compilation units is determined. + // This sync point can be re-enabled if RocksDB can control the + // initialization order of any/all static options created by the user. // TEST_SYNC_POINT("Block::~Block"); }