fanquake 3c856e2fe8
Merge bitcoin/bitcoin#28569: log: Don't log cache rebalancing in absense of a snapshot chainstate
ec84f999f1408b7f1ff4498f78c33b34c30e934c 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 ec84f999f1408b7f1ff4498f78c33b34c30e934c
  glozow:
    concept ACK ec84f999f1408b7f1ff4498f78c33b34c30e934c, don't have opinions other than removing confusing log
  theStack:
    utACK ec84f999f1408b7f1ff4498f78c33b34c30e934c

Tree-SHA512: 30bbfc648e7c788106f78d52e47a3aa1e1874f65d13743643dc50bcf7f450d8330711ff9fdeac361722542da6051533153829c6d49033227ed315e111afc899f
2023-10-20 14:39:34 +01:00
..
2023-10-12 11:27:19 +02:00
2023-10-12 11:27:19 +02:00
2023-08-08 17:50:41 +02:00
2023-09-19 16:38:08 +02:00
2023-09-27 15:05:15 -04:00
2023-10-12 11:27:19 +02:00
2023-10-12 11:27:19 +02:00
2023-10-12 11:27:19 +02:00
2023-06-16 10:38:19 +01:00
2023-06-16 10:38:19 +01:00
2023-09-19 16:38:08 +02:00
2023-10-12 11:27:19 +02:00
2023-06-16 10:38:19 +01:00
2023-09-13 11:37:45 +01:00
2023-10-12 11:27:19 +02:00
2023-10-12 11:27:19 +02:00
2023-06-16 10:38:19 +01:00
2023-07-19 18:12:42 +02:00
2023-10-12 11:27:19 +02:00