Skip to content

Commit

Permalink
Fix sync-point comment in Block destructor (#4380)
Browse files Browse the repository at this point in the history
Summary:
This is a follow up to #4370. The earlier comment is not correct.

Thanks to ajkr for pointing this out.
Pull Request resolved: #4380

Differential Revision: D9874667

Pulled By: sagar0

fbshipit-source-id: f4e092d86b29c715258210b770643d367e38caae
  • Loading branch information
sagar0 authored and facebook-github-bot committed Sep 17, 2018
1 parent dfda910 commit ac46790
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions table/block.cc
Original file line number Diff line number Diff line change
Expand Up @@ -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");
}

Expand Down

0 comments on commit ac46790

Please sign in to comment.