mirror of
https://github.com/ethereum/go-ethereum.git
synced 2026-02-26 15:47:21 +00:00
48ec86abbb
I added the history mode configuration in eth/ethconfig initially, since it seemed like the logical place. But it turns out we need access to the intended pruning setting at a deeper level, and it actually needs to be integrated with the blockchain startup procedure. With this change applied, if a node previously had its history pruned, and is subsequently restarted **without** the `--history.chain postmerge` flag, the `BlockChain` initialization code will now verify the freezer tail against the known pruning point of the predefined network and will restore pruning status. Note that this logic is quite restrictive, we allow non-zero tail only for known networks, and only for the specific pruning point that is defined. |
||
|---|---|---|
| .. | ||
| testdata | ||
| accountcmd.go | ||
| accountcmd_test.go | ||
| attach_test.go | ||
| chaincmd.go | ||
| config.go | ||
| consolecmd.go | ||
| consolecmd_test.go | ||
| dbcmd.go | ||
| exportcmd_test.go | ||
| genesis_test.go | ||
| logging_test.go | ||
| logtestcmd_active.go | ||
| logtestcmd_inactive.go | ||
| main.go | ||
| misccmd.go | ||
| run_test.go | ||
| snapshot.go | ||
| verkle.go | ||
| version_check.go | ||
| version_check_test.go | ||