cp: stageloop, execmodule: add ERIGON_IN_MEM_HISTORY env flag for in-mem history reads (#20245)#20262
Merged
Merged
Conversation
- StageLoopIteration (ExecV3 live exec path) - ValidateChain (fork validation path) - updateForkChoice (FCU path) Previously only ProcessFrozenBlocks respected the env flag.
AskAlexSharov
approved these changes
Apr 2, 2026
AskAlexSharov
pushed a commit
that referenced
this pull request
Apr 6, 2026
…mem history reads (#20245) (#20262) Cherry-pick of #20245 to `release/3.4`. **Conflict resolution**: `execution/execmodule/executor.go` doesn't exist in `release/3.4` (the `PipelineExecutor` abstraction was introduced in `main` after the branch point). The equivalent change — adding the `ERIGON_IN_MEM_HISTORY` env flag and wiring it to `SetInMemHistoryReads` — was applied to `execution/stagedsync/stageloop/stageloop.go` which is the relevant call site in `release/3.4`.
github-merge-queue Bot
pushed a commit
that referenced
this pull request
Apr 6, 2026
Cherry-pick from release/3.4 to main. Original PRs: - #20335 — paged writer: lost amount of workers - #20281 — pagedWriter and compressor to use same COMPRESS_WORKERS variable - #20262 — stageloop, execmodule: add ERIGON_IN_MEM_HISTORY env flag - #20114 — crypto: zero-alloc, syncpool-free method to hash []byte type - #20194 — execution/state: revert CodeSizePath in codeChange journal entry 20 candidates checked total; 15 were already effectively on main. --------- Co-authored-by: moskud <sudeepdino008@gmail.com> Co-authored-by: awskii <awskii@users.noreply.github.com> Co-authored-by: Giulio rebuffo <giulio.rebuffo@gmail.com> Co-authored-by: lystopad <oleksandr.lystopad@erigon.tech> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
AskAlexSharov
pushed a commit
that referenced
this pull request
Apr 18, 2026
…mem history reads (#20245) (#20262) Cherry-pick of #20245 to `release/3.4`. **Conflict resolution**: `execution/execmodule/executor.go` doesn't exist in `release/3.4` (the `PipelineExecutor` abstraction was introduced in `main` after the branch point). The equivalent change — adding the `ERIGON_IN_MEM_HISTORY` env flag and wiring it to `SetInMemHistoryReads` — was applied to `execution/stagedsync/stageloop/stageloop.go` which is the relevant call site in `release/3.4`.
AskAlexSharov
pushed a commit
that referenced
this pull request
Apr 18, 2026
…mem history reads (#20245) (#20262) Cherry-pick of #20245 to `release/3.4`. **Conflict resolution**: `execution/execmodule/executor.go` doesn't exist in `release/3.4` (the `PipelineExecutor` abstraction was introduced in `main` after the branch point). The equivalent change — adding the `ERIGON_IN_MEM_HISTORY` env flag and wiring it to `SetInMemHistoryReads` — was applied to `execution/stagedsync/stageloop/stageloop.go` which is the relevant call site in `release/3.4`.
github-merge-queue Bot
pushed a commit
that referenced
this pull request
Apr 20, 2026
Cherry-pick from `release/3.4` to `main`: - #20635 db/state: fix MaxStep using MinTxNum in DomainRoTx.prune - #20639 dbg.SaveHeapProfileNearOOMPeriodically() call in all sub-commands - #20571 blk-range: wrong logs - #20565 merge: set merge workers to 1 - #20576 simplify user-visible logs - #20518 cp related PRs for "don't query in db, what is in files" - #20517 teach: Unwind beyond data in snapshots not allowed - #20368 rpc: use synctest for TestClientCancelHTTP to fix CI flakiness - #20329 logs: move some Info logs to Debug level - #20262 stageloop, execmodule: add ERIGON_IN_MEM_HISTORY env flag for in-mem history reads --------- Co-authored-by: bendertherobert <bendertherobert@gmail.com> Co-authored-by: moskud <sudeepdino008@gmail.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: info@weblogix.biz <admin@10gbps.weblogix.it>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-pick of #20245 to
release/3.4.Conflict resolution:
execution/execmodule/executor.godoesn't exist inrelease/3.4(thePipelineExecutorabstraction was introduced inmainafter the branch point). The equivalent change — adding theERIGON_IN_MEM_HISTORYenv flag and wiring it toSetInMemHistoryReads— was applied toexecution/stagedsync/stageloop/stageloop.gowhich is the relevant call site inrelease/3.4.