Question - Was the Receipts table left intentionally in MDBX after the migration to V2

[zhk101]

Describe the bug

Correct me if I am wrong, but I understand that the migration, among other things, also moved the receipts to the static files. But Here there is no clearing of the Receipts table in MDBX.

I tried clearing that table on my node and recompacting (after the migration v2) and I managed to claim back a few hundreds GiB. Then did some quick sanity and recent and old receipts are still retrievable.

Steps to reproduce

Run migration v2 command, then

./reth-bsc db --chain bsc clear mdbx Receipts

mkdir -p $NODE_DATA_DIR/db_new
./reth-bsc db --chain bsc copy --compact --force-dynamic-size $NODE_DATA_DIR/db_new/mdbx.dat

cp $NODE_DATA_DIR/db/database.version  $NODE_DATA_DIR/db_new/
rm -rf $NODE_DATA_DIR/db
mv $NODE_DATA_DIR/db_new $NODE_DATA_DIR/db

Node logs

Platform(s)

Linux (x86)

Container Type

Not running in a container

What version/commit are you on?

cb902b4

What database version are you on?

cb902b4

Which chain / network are you on?

BSC/56

What type of node are you running?

Pruned with custom reth.toml config

What prune config do you use, if any?

--prune.transactionlookup.distance=5760000 \
--prune.receipts.distance=5760000 \
--prune.accounthistory.distance=5760000 \
--prune.storagehistory.distance=5760000 \
--prune.bodies.distance=5760000 \
--prune.senderrecovery.full \

If you've built Reth from source, provide the full command you used

make maxperf

Code of Conduct

• I agree to follow the Code of Conduct

[chee-chyuan]

Good find! It does seem like the Receipts aren't cleared. I have yet to give it a try myself. The upstream reth seems to also exhibits the same behaviour. I will need to deep dive into this alot more but from this issue paradigmxyz/reth#24591 it does seem that the Receipt table might not be behaving as it should