5 Commits (2e8e35f2ada60e8e90aff8f6374ea7cd7da16116)

Author	SHA1	Message	Date
rjl493456442	f46c878441	core/rawdb: implement in-memory freezer (#29135)	10 months ago
Jakub Freebit	447945e438	core/rawdb: add logging and fix comments around AncientRange function. (#28379) ... This adds warning logs when the read does not match the expected count. We can also remove the size limit since the function documentation explicitly states that callers should limit the count.	1 year ago
rjl493456442	3853f50082	trie/triedb/pathdb, core/rawdb: enhance error message in freezer (#28198) ... This PR adds more error message for debugging purpose.	1 year ago
rjl493456442	7de748d3f6	all: implement path-based state scheme (#25963) ... * all: implement path-based state scheme * all: edits from review * core/rawdb, trie/triedb/pathdb: review changes * core, light, trie, eth, tests: reimplement pbss history * core, trie/triedb/pathdb: track block number in state history * trie/triedb/pathdb: add history documentation * core, trie/triedb/pathdb: address comments from Peter's review Important changes to list: - Cache trie nodes by path in clean cache - Remove root->id mappings when history is truncated * trie/triedb/pathdb: fallback to disk if unexpect node in clean cache * core/rawdb: fix tests * trie/triedb/pathdb: rename metrics, change clean cache key * trie/triedb: manage the clean cache inside of disk layer * trie/triedb/pathdb: move journal function * trie/triedb/path: fix tests * trie/triedb/pathdb: fix journal * trie/triedb/pathdb: fix history * trie/triedb/pathdb: try to fix tests on windows * core, trie: address comments * trie/triedb/pathdb: fix test issues --------- Co-authored-by: Felix Lange <fjl@twurst.com> Co-authored-by: Martin Holst Swende <martin@swende.se>	2 years ago
rjl493456442	79a478bb61	core/rawdb: implement resettable freezer (#26324) ... This PR implements resettable freezer by adding a ResettableFreezer wrapper. The resettable freezer wraps the original freezer in a way that makes it possible to ensure atomic resets. Implementation wise, it relies on the os.Rename and os.RemoveAll to atomically delete the original freezer data and re-create a new one from scratch.	2 years ago