You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Will a full or pruned node lose the ability to migrate receipts from the database to a static file?
Yea, whenever there's a prune configuration for receipts, they are written to database, and remain there. Each specific static file range requires all data to be present and sequential.
Pruning by distance (aka gradually delete old receipts): deleting/truncating old receipts from a single static file is expensive, since they're at the head of the file. We could prune only files and not single receipts from files. (eg. delete the whole file of 0 -> 499_999 when its time to delete receipt 499_999, instead of slowling deleting receipts from it), but hasn't been worth it yet imo.
Pruning by logs is the most difficult one though. We rely on TxNumber to query receipts/transactions. However, this pruning type implies that receipts have gaps inbetween them and static files assume that they are sequential in order to query them.
Describe the change
just like issue: #10118
it seems by design, see the following code, crates/static-file/static-file/src/static_file_producer.rs
if any prune config is set, we will get a none receipts target:
Is my understanding correct?
Additional context
No response
The text was updated successfully, but these errors were encountered: