gc: keep track of available checkpoints
Currently, the checkpoint iterator is in fact a wrapper around memtx_engine::snap_dir while the garbage collector knows nothing about checkpoints. This feels like encapsulation violation. Let's keep track of all available checkpoints right in the garbage collector instead and export gc_ API to iterate over checkpoints.
Showing
- src/box/CMakeLists.txt 0 additions, 1 deletionsrc/box/CMakeLists.txt
- src/box/box.cc 28 additions, 22 deletionssrc/box/box.cc
- src/box/checkpoint.c 0 additions, 72 deletionssrc/box/checkpoint.c
- src/box/checkpoint.h 0 additions, 97 deletionssrc/box/checkpoint.h
- src/box/gc.c 76 additions, 16 deletionssrc/box/gc.c
- src/box/gc.h 60 additions, 8 deletionssrc/box/gc.h
- src/box/lua/info.c 3 additions, 7 deletionssrc/box/lua/info.c
- src/box/memtx_engine.c 7 additions, 0 deletionssrc/box/memtx_engine.c
- src/box/vinyl.c 1 addition, 2 deletionssrc/box/vinyl.c
- src/box/vy_scheduler.c 0 additions, 1 deletionsrc/box/vy_scheduler.c
Loading
Please register or sign in to comment