Gyuho Lee 5165344981 mvcc: use latest revision to tombstone
We replace/insert into in-memory B-tree, which means
we only keep a single node per key thus do not support
delete by revision on B-tree. So, (*keyIndex).tombstone
has always been marked with latest revision.

tombstone with key's modified revision panics:

panic: store.keyindex: put with unexpected smaller revision [{2 0} / {2 0}]

Signed-off-by: Gyuho Lee <gyuhox@gmail.com>
2018-05-09 09:07:39 -07:00
..
2018-05-04 13:15:51 -07:00
2018-02-26 17:11:40 -08:00
2018-02-26 17:11:40 -08:00
2018-05-04 13:15:51 -07:00
2018-05-04 13:15:51 -07:00
2018-04-16 17:36:00 -07:00
2018-02-26 17:11:40 -08:00
2018-02-26 17:11:40 -08:00
2018-05-04 13:15:51 -07:00
2018-02-26 17:11:40 -08:00
2018-02-26 17:11:40 -08:00
2018-05-04 13:15:51 -07:00
2018-02-26 17:11:40 -08:00