Skip to content

Commit 3c856e2

Browse files
committed
Merge bitcoin/bitcoin#28569: log: Don't log cache rebalancing in absense of a snapshot chainstate
ec84f99 log: Don't log cache rebalancing in absense of a snapshot chainstate (Fabian Jahr) Pull request description: I have noticed that this log now is always printed, even if there is no snapshot chainstate present or even was present. I think this is confusing to users that have never even thought about using assumeutxo since in that case the rebalancing is just ensuring the normal environment with one chainstate. So I suggest we don't log in absence of a snapshot chainstate. We could also think about rewording the message instead but I think this is simpler. ACKs for top commit: stickies-v: utACK ec84f99 glozow: concept ACK ec84f99, don't have opinions other than removing confusing log theStack: utACK ec84f99 Tree-SHA512: 30bbfc648e7c788106f78d52e47a3aa1e1874f65d13743643dc50bcf7f450d8330711ff9fdeac361722542da6051533153829c6d49033227ed315e111afc899f
2 parents fc1073b + ec84f99 commit 3c856e2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/validation.cpp

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5711,8 +5711,8 @@ void ChainstateManager::MaybeRebalanceCaches()
57115711
assert(ibd_usable || snapshot_usable);
57125712

57135713
if (ibd_usable && !snapshot_usable) {
5714-
LogPrintf("[snapshot] allocating all cache to the IBD chainstate\n");
5715-
// Allocate everything to the IBD chainstate.
5714+
// Allocate everything to the IBD chainstate. This will always happen
5715+
// when we are not using a snapshot.
57165716
m_ibd_chainstate->ResizeCoinsCaches(m_total_coinstip_cache, m_total_coinsdb_cache);
57175717
}
57185718
else if (snapshot_usable && !ibd_usable) {

0 commit comments

Comments
 (0)