Skip to content

Commit 5db7d4d

Browse files
committed
doc: Correct docstring describing max block tree db cache
It is always applied in the same way, no matter how the txindex is setup. This was no longer accurate after 8181db8, where their initialization was made independent.
1 parent 37e49c2 commit 5db7d4d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/txdb.h

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,11 +27,11 @@ static const int64_t nDefaultDbCache = 450;
2727
static const int64_t nDefaultDbBatchSize = 16 << 20;
2828
//! min. -dbcache (MiB)
2929
static const int64_t nMinDbCache = 4;
30-
//! Max memory allocated to block tree DB specific cache, if no -txindex (MiB)
30+
//! Max memory allocated to block tree DB specific cache (MiB)
3131
static const int64_t nMaxBlockDBCache = 2;
32-
//! Max memory allocated to block tree DB specific cache, if -txindex (MiB)
3332
// Unlike for the UTXO database, for the txindex scenario the leveldb cache make
3433
// a meaningful difference: https://github.com/bitcoin/bitcoin/pull/8273#issuecomment-229601991
34+
//! Max memory allocated to tx index DB specific cache in MiB.
3535
static const int64_t nMaxTxIndexCache = 1024;
3636
//! Max memory allocated to all block filter index caches combined in MiB.
3737
static const int64_t max_filter_index_cache = 1024;

0 commit comments

Comments
 (0)