Hi there, I’ve been exploring the WithNumVersionsToKeep() alongside badger’s stream api and the behavior Im seeing is that for any WithNumVersionsToKeep(n) where n > 1, badger keeps n + 1. Badger v2.2007.2 func main() { opts := badger.DefaultOptions("/tmp/badger").WithNumVersionsToKeep(2) db, er…

Hey @seanlaff , thanks for reaching out. When you flush a DB, all the keys which are at or below discardTs can be discarded from the LSM tree (see here ). When badger is run in unmanaged mode, this discardTs is governed by read timestamp (readTs). Each transaction calls txn.Discard() and hence update…

Badger keeping n+1 versions when using WithNumVersionsToKeep(n)

Issues Badger

Topic		Replies	Views
Keeping key version when adding same key on the same transaction Badger kind:question	3	660	September 24, 2020
Badger Documentation limited or Feature removed? Badger kind:question , status:accepted	10	753	December 21, 2020
Question: Badger key version consistency among raft followers Badger	8	917	August 26, 2020
Request option to write multiple versions in a single batch Badger	3	965	April 5, 2021
Managed mode and lost keys after crash Badger area:data-loss	4	926	June 17, 2021

Badger keeping n+1 versions when using WithNumVersionsToKeep(n)

Related topics