rockeet

> Is this related to #10487? It seems doing an iterator refresh with snapshot could free the pinned resources. Yes, this issue has some relation to #10487, but #10487 needs...

> I am confused as to the advantage of this change. The existing code uses a unique ptr to store the moved unique ptr. The proposal uses a raw pointer...

This issue has been resolved by PR #10593

> Can you assign me this issues? Maybe I want to try to solve this issue. Very thanks for your contribution!

1. This error does not affect whole ToplingDB. 2. Import your `rsa pubkey` to github, the `clone` will success.

You can file an issue about the clone fail, I can change the `git@` to `https://` in Makefile.

I seeked for a feature to avoid creating new iterator when I need to update an iterator to a specified snapshot, then I found Refresh, I expect Refresh is much...

> Hi @rockeet, I agree this is a reasonable feature to add, and optimizing the part where superversion is not changed should be easier to implement. It's not planned yet,...

@LucienXian Our in house branch([link]()) have a [fix](https://github.com/topling/toplingdb/commit/76da3562468f954d772bb36b9362f11655a39922) for this issue: if set `level0_file_num_compaction_trigger

> > level0_file_num_compaction_trigger > > @rockeet Does simply setting level0_file_num_compaction_trigger affect the L0->Lbase compaction decision behavior? Yes, just level0_file_num_compaction_trigger effect Intra-L0 compaction, with my [fix](https://github.com/topling/toplingdb/commit/76da3562468f954d772bb36b9362f11655a39922), Intra-L0 compaction can be disabled...