4 commits

Author	SHA1	Message	Date
0xb10c	799968e8b3	tracing: misc follow-ups to 22902 ... - mention 'Lost X events' workaround - clarify flush tracepoint docs - fix typo in tracepoint context - clarify flush for prune The documentation and examples for the `fFlushForPrune` argument of the utxocache flush tracepoint weren't clear without looking at the code. See these comments: https://github.com/bitcoin/bitcoin/pull/22902#issuecomment-987094612 - doc: note that there can be temporary UTXO caches Bitcoin Core uses temporary clones of it's _main_ UTXO cache in some places. The utxocache:add and :spent tracepoints are triggered when temporary caches are changed too. This is documented.	2022-02-18 20:48:52 +05:30
Arnab Sen	36a6584703	tracing: correctly scope utxocache:flush tracepoint ... Previously, the `utxocache:flush` tracepoint was in the wrong scope and reached every time `CChainState::FlushStateToDisk` was called, even when there was no flushing of the cache. The tracepoint is now properly scoped and will be reached during a full flush. Inside the scope, the `fDoFullFlush` value will always be `true`, so it doesn't need to be logged separately. Hence, it's dropped from the tracepoint arguments.	2021-12-30 19:30:17 +05:30
Arnab Sen	2bc51c5c32	[tracing] tracepoints to utxocache add, spent and uncache ... Signed-off-by: Arnab Sen <arnabsen1729@gmail.com>	2021-11-28 11:51:21 +05:30
Arnab Sen	a26e8eef43	[tracing] tracepoint for utxocache flushes ... Signed-off-by: Arnab Sen <arnabsen1729@gmail.com>	2021-11-28 11:34:44 +05:30