Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pruned mode: prune transaction data #2616

Open
sistemd opened this issue Feb 21, 2025 · 0 comments · May be fixed by #2637
Open

Pruned mode: prune transaction data #2616

sistemd opened this issue Feb 21, 2025 · 0 comments · May be fixed by #2637
Assignees

Comments

@sistemd
Copy link
Contributor

sistemd commented Feb 21, 2025

When pruned mode is enabled, delete all data from transactions and transaction_hashes tables that goes further back than the configured history value. This should probably not be done on every new block that gets inserted, but rather should be batched either every X minutes or only happen every X blocks. It is likely that this pruning can be entirely implemented in the storage layer.

@sistemd sistemd mentioned this issue Feb 21, 2025
5 tasks
@sistemd sistemd changed the title Prune transaction data in light mode (easy, big win) Light mode: prune transaction data Feb 21, 2025
@sistemd sistemd changed the title Light mode: prune transaction data Pruned mode: prune transaction data Feb 21, 2025
@sistemd sistemd self-assigned this Feb 21, 2025
@sistemd sistemd linked a pull request Feb 27, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant